LiveCycle ES2 and ES3 both support Oracle 11g. There have been reports of LiveCycle customers experiencing the following database connectivity failure intermittently even when the database is running and the data source has been configured properly for LiveCycle connectivity:
WARN [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@2b739450
java.sql.SQLRecoverableException: Io exception: Software caused connection abort: recv failed
In some cases this failure has been linked to Oracle Thin Client bug 9373409 (see https://forums.oracle.com/forums/thread.jspa?threadID=2425542 for more details). The issue appears to be related to the driver failing on Windows Vista and 2008 systems. The fix is to upgrade the Oracle driver to version 220.127.116.11.
Also, to reduce the impact of these type of connection interruptions on LiveCycle process execution, you can apply auto-reconnect configuration to the data source. This will not resolve the connection problem but it usually allows transactions to eventually succeed when they would otherwise fail. More information on how this can be configured in JBoss can be found here: http://blogs.adobe.com/livecycle/2011/03/setting-up-jboss-to-auto-reconnect-after-database-outage.html