Archives of the TeradataForum

Message Posted: Wed, 02 Jan 2002 @ 19:22:39 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

We may be a little biased also, cause 4.1 was the worst we've had to deal with, so far. Segmentation violations (resulting in TPA resets); PMON "View SQL" button (affectionately re-named the "TPA Reset" button) causing TPA resets when selected (There must've been a sale on TPA reset code; stored procedures causing looping segmentation violations; and, CASE statement truncating results.

Another major problem was that fixes issued to correct a problem have generally resulted in the creation of a new problem so that the fix had to be backed out, or live with the new problem. .18 caused the stored procedure problem. We're just now getting ready to try .26 (but only after others have been on the bleeding edge). We averted a problem with .22 at the last minute due to problems encountered by other customers.

	<Prev	Next>		<<First	<Prev	Next>	Last>>