Phil,
We have systems that have an up time of more that a year without
any problems and without knowing your system its hard to diagnose
what is going on.
Are you running queries through Process or the Command line; or are you kicking off the Transformation through some Server software.
Are you implementing external connection pools ?? It not you probably should at least so you can monitor open/close connections.
In out External Pool connection, we cycle cached connections back to the Server every 30 min or so just to make sure they are fresh and on any error, the connection gets closed. I know that Sybase Server, if you previously had an error on a connection, i.e. Syntax error on an SQL Statement, that connection won't return any queries until the error stack is read from the db. The release connection on any error was the fix for that.
-JG
Phil Friedman wrote:
It seems that after a large number --hundreds, but I have not counted-- of queries on the same db connection, the SQL extension starts returning empty result sets with no errors thrown.
I'm at 2.6.0 connecting to Sybase SQL Anywhere 8. There are no problems with the SQL as I've run similar statements earlier and can restart and run the same statements w/o errors later.
Any ideas on what to look for? Regards, Phil Friedman - Terralink Software - 1-207-772-6500 x101
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
