Re: SQL ERROR 408 Need GURU HELP !!!

I have experienced the SQL ERROR 408 on verion 5.00.UC2 of online running on hp-ux 9.00. In our case it is usually down to the value calculated by the cost optimizer being converted by the os from a float to an integer. The problem may occur for a range of values and the work around is to make the cost optimizer evlaute a value outside of this range. (hope you are following me so far.) If you SET EXPLAIN ON you should be able to see where the problem lies, and then by adjusting the systables.nrows value for the problem table the cost optimizer will calculate a different value, and thus solve the problem. If you then UPDATE STATISTICS on the table the problem may come back is the actual number of rows hasn't changed significantly. We have been told that the problem is rectified in version 5.02. and upgrading the os to hp-ux 9.04. We have done this, on our backup/history box but have found another problem, but that's a diffent story altogether... David Watts. (I hope this is of some help).