On Mon, 4 Aug 2003 19:11:19 -0400, Matthew O. Persico wrote: >On 04 Aug 2003 15:33:51 +0200, Michael Peppler wrote: >>On Sun, 2003-08-03 at 08:10, Matthew O. Persico wrote: >>>I'm getting flaky behaviour from one query. It will fail with a tds >>>token error, but it cannot be recreated on the next run for the >>>same data. To wit: >>> >>>20030803.02:01:34: Portia::Utils::portfolioInfo >>>: Cannot execute statement >><snip> >>>: handleType => statement >>>: OpenClient message: LAYER = (4) ORIGIN = (1) SEVERITY = (5) >>>NUMBER = (28) >>>: Message String: ct_results(): protocol specific layer: external >>>error: There is a tds protocol error. An illegal token was >>>received. >>>: Stopped >>>: => at /am/common/lib/site_perl/5.6.1/Portia/Utils.pm line >>>431 >>> >>>Perl 5.6.1 >>>Adaptive Server Enterprise/12.0.0.7/P/EBF 10869 ROLLUP/Sun_svr4/OS >>>5.6/1996/32bit/FBO/Fri Feb 21 03:19:58 2003 >>>DBD::Sybase 1.00 >>>DBI 1.37 >> >>First things first: Have you checked the error log for the ASE >>server? >>There may be a clue there as to why this is failing. > >DUH!!!!! Of course not. That would have been smart! Just because the >last time I had problems with this query there was no error in the >logs doesn't mean there ain't one there now. File this >under the category of > > First, check that it's plugged in and turned on. > >:-( >-- Followup - known problem on Syb 12.0 and Solaris. From my SA's Change Order:
In order to eliminate the "illegal tds token sequence was received" messages that Sybase 12.x dataservers have been producing, Sybase has recommended increasing value of the tcp_ip_abort_interval parameter to more than 960000. Let's try 1200000 on <machine names removed> -- Matthew O. Persico
