From what I've been told, this has been happening for the past week or so. We're not aware of any changes on the i or in any SQL code on the front-end. It seems that there is no single SQL statement that causes this issue, as the error will suddenly appear when performing an SQL statement (but not always). The SQL commands are issued through a JDBC connection.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact