Our system does not have a single line of sql in application code. Everything is wrapped up in packages and stored procedures. The smallest schema I am testing liquibase at the moment has 54 packages, with average 200 lines of sql.
Problem is with initial import of this schema. 9 out of 10 times when I try to do a clean install (which is required for all developers on daily basis) I'm getting
Liquibase Home: /usr/lib/liquibase
Liquibase update Failed: java.sql.SQLRecoverableException: No more data to read from socket
This is a sign that application (liquibase) is trying to check out a connection which has "timed out" or "staled" which has to be handled on liquibase side.
CentOS release 6.4 (Final)
Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
PL/SQL Release 10.2.0.4.0 - Production
Oracle Instant Client 11.2 ojdbc6
Added better connection handling. Should be resolved