Did you also think about getting a different (one-off) database connection for executing the DDL?

What a fantastic idea!! Which is why that is exactly what I did The whole reason of doing the suspend/resume is actually to make sure we get a new Connection from the DataSource. The ConnectionReleaseMode has no bearing on this.

Anyway, please try the 5.2 snapshot and see if you see that fixes the problem. Or wait for Gail Badner to finish the 5.1 backport and try that snapshot. As far as I am concerned, this is fixed unless I hear otherwise.