<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Greetings,<br>
<br>
Here is what I have surmised thus far.<br>
<br>
1) The behavior on different nodes is still a mystery.<br>
<br>
2) The error has to do with the RUN 10 parameters of
calib_user.RunIndexg12_mk, specifically the system
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
SC_CALIBRATIONS.<br>
<br>
3) This error was not present prior to August, in fact multiple
users had used the calib_user.RunIndexg12_mk table for billions of
simulated, equating to greater than 10,000 jobs on the farm, all
successful previously.<br>
<br>
4) I was able to make calib_user.RunIndexg12_mkIII, with all the
parameters of calib_user.RunIndexg12_mk, except for the system
SC_CALIBRATIONS, which is left to its default value. Running jobs on
this runindex does not result in error.<br>
<br>
5)There is a difference in output from the simulations between the
two different runindexes, calib_user.RunIndexg12_mk and
calib_user.RunIndexg12_mkIII. <br>
<br>
6) Noticing the behavior that the error is caused by one system in
the runindex leads to me question why some nodes will not throw
fault error while others will. Supposedly there is no difference in
the builds, nor the build of mysql on each node. What sets this
error off in some nodes and not others? Also, why did this occur
after August 16 2014?<br>
<br>
<br>
BR<br>
MK<br>
<br>
</body>
</html>