Pure SQL Exception encountered.
This problem is related to the database connections used in the BPEL/ESB projects. Usually sometimes we encounter this problem when the database on which we are doing some operations or the database(dehydration store) on which BPEL and ESB schemas are created is refreshed/restarted, and SOA Server doesn't come to know about the refresh/restart.
** This problem is seen when we use direct database connection instead of JNDI. It is always recommended to use JNDI instead of direct database connections.
Bounce the SOA server so that the SOA Server updates itself.