ORA-03135: connection lost contact Either your server connection was terminated unexpectedly or your server timed out the connection.
Check if the SQLNET.INBOUND_CONNECT_TIMEOUT in sqlnet.ora is not set too low.
If this is not a problem, check if you have firewall issues. Some routers are set up to clean up idle TCP connections.
 Forum Messages
Hi frenz,
I have installed informatica version 7.1.4 and DAC version 7.9.3.
While configuring DAC it is giving the following error frequently while performing any operation like saving a record, synchronize the tasks etc..
Error while verifying existence of record with the same unique id.
MESSAGE:::java.sql.SQLException: ORA-03135: connection lost contact
EXCEPTION CLASS::: com.siebel.etl.database.IllegalSQLQueryException
com.siebel.etl.database.DBUtils.executeQuery(DBUtils.java:507)
com.siebel.etl.database.WeakDBUtils.executeQuery(WeakDBUtils.java:268)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.verifyNoRecordWithKeyCombination(UpdatableDataObject.java:327)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.verifyNoRecordWithKeyCombination(UpdatableDataObject.java:298)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.verifyNoRecordWithKeyColumns(UpdatableDataObject.java:153)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.verifyNoRecordWithKeyColumns(BaseDACObject.java:160)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.canBeCreated(UpdatableDataObject.java:146)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.canBeCreated(BaseDACObject.java:139)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.create(BaseDACObject.java:532)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.createUpdate(UpdatableDataObject.java:210
Thanks & Regards,
Madhavi.P |
| : -> 05-FEB-2008 10:49:24 | Possible causes | DbMotive | Reply |
This might be a version problem.
What version of the Oracle client are you using. Does this match the database version?
It can also be a problem when your database is configured to run in UTF8 mode, but your client character set is not compatible.
Most of the time this can be noiced when using varchar2(4000) columns |
Add your message for ORA-03135
| 
Home