Hi Ben, thanks for your reply. I can confirm that your suggested workaround does indeed make the problem dissapear. I guess this issue hasn't been seen at T2K since we use MYSQL for the history. Thanks, Nick.