This content has been marked as final. Show 3 replies
Can you check the profile settings (IDLE_TIME setting) for the logged in user at Oracle level?
This could also be due to failure of connection pooling feature at your middle tier.
It could also occur due to network problems (firewalls/antivirus software dropping your packets and terminating the connections).
I don't know how to check the IDLE_TIME for the logged in user, but IDLE_TIME is expressed in minutes and I get this error in 2-5 seconds.
I exclude network problems because I get this error even when running the code on the server using SQL Developer, not only from the application and other complex functions and procedures are working fine if they don't use columns with type NUMBER(1,0) in where statements.
Thx for your answer.
Can you upgrade your database to 10.2.0.3.0 or 10.2.0.4.0? It could be a bug in 10.2.0.1 which is fixed in later patches. Worth a try.
Also try searching on Metalink if your application is using JDBC or OCI. Otherwise, you should be getting in touch with Oracle Support for this issue.