Environment:
Oracle 11.2.0.3 EE on Solaris 10
I have an environment where a Pentaho instance is loading data into the Oracle database. The load action opens a database connection, reads some data and then takes a long time (60-90 minutes) to process the data and then attempts to write the data to the database using the same connection.
We are seeing a timeout error: "Io exception: Connection timed out" coming out of Pentaho after about 60 minutes.
I have the following settings in SQLNET.ORA:
SQLNET.EXPIRE_TIME=120
The firewall settings have been verified to not include anything that would terminate a connection after 60 minutes.
I would like to learn more about the disconnection that seems to be happening from the database side.
What auditing option/command/setting can be sued to gather more detail about when the database senses a disconnected or idle process and hence terminates the connection?
Thanks very much!!
-gary