Hi Stephen, > -----Original Message----- > From: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 19. September 2002 06:51 [description of two problems snipped]
I try to summarize the differences between the new and the old configuration: - separate DB server => socket communication instead of shared memory - .NET ODBC data provider instead of ?? (ADO, RDO?) => different ODBC calls - ODBC driver: build 25 vs build 28 Do I get all? ODBC calls stall: > even stand-alone WSH agents will stall. Does this mean, even a separate started ODBC application stalls (e.g. SQLStudio)? The stall problems smells like a resource problem, where, after a time out, all is going on. - How often do connects occur? - How long is the time out period of a ODBC connection? - How is the kernel parameter set (SESSION_TIMEOUT)? - Do time outs happen during normal usage? Do they happen before the stalling? If a time out has happened, ODBC tries to reconnect transparently for the client application. But there are problem, e.g. after a time out during fetch the next fetch after reconnect fails since the result set is no longer existing. crash in ODBC: maybe a debug version of the driver can help. I'll send one to you. > Help! > ======= > A problem that happens only 10 minutes out of every 4 days is > not easy to > track down. Are there suggestions on what I can do? I have > eliminated > everything but the ODBC driver. > > I have already gone so far to put wrappers around all my > SELECT / INSERT / > UPDATE / DELETE statements and measure the time. Anytime a > query takes more > than it should, I get alerted via pager. The last time I was > able to get in > while problem was going on, I saw only 5 active sessions and > database in > normal state (connect possible, not full, etc.) Besides the alert you could switch on the vtrace and switch it off afterwards. In the vtrace the SQL statement in charge would be visible and maybe more important whether a new connection was made. > > Is there any way to study the internal workings of the ODBC driver? You can switch on the driver trace, but it would slow down things considerably and would produce huge traces in four days. The vtrace only made in case of the stall problem is probably the best, at least as first step. I hope we are going in the right direction to find the problem. Regards Thomas ---------------------------------------------- Dr. Thomas K�tter SAP DB, SAP Labs Berlin SAP DB is open source. Get it! www.sapdb.org _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
