|
Archives of the TeradataForumMessage Posted: Thu, 19 Aug 2004 @ 08:42:28 GMT
Hello, Now we know what's going on ! Some of our MicroStrategy reports crashed with 3610-error. NCR advised a work-around to this problem, putting "diagnostic noltstj on for session" Unfortunately this changes the plan for the SQL-request in question !!! The 3610-error is adressed by DR 87855, which has a fix that's currently being tested. Maybe we should play with the "diagnostic noltstj on for session". It might come up with a better plan in some cases... Any comments from NCR ? Best Regards
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||