This one turned out to be a kernel bug present in MaxDB 7.5.0.5 and should be fixed in 7.5.0.6 I just updated the MaxDB version to 7.5.0.8 and everything works fine now.
Regards, Andreas Schroeder -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
