A customer who is using FME to connect to our recently upgraded database is reporting that a process for pulling data that was working before the upgrade now seems to just hang after a few minutes. We have SQLNET.EXPIRE_TIME=4 in the server's sqlnet.ora which means we check for dead sessions at 4 minutes. The FME log does not report any errors. It just stops logging and performs no more work.
Question
Is there a recommended setting for SQLNET.EXPIRE_TIME when using FME with an Oracle 12c database?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+15- Safer
@dmallard, you may wish to see if the timeout works on the Server side. I'm wondering if the process is getting disconnected.
See: https://knowledge.safe.com/questions/46477/oracle-12c-bad-packet-error-resolution.html
Let us know if you resolved this some other way.
Regards,
Steve
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.