oacle connection

i am developing a web and desktop application which connects to the oracle database remotely. it connects ok. But gets disconnected very often with out error, both client and severs is windows 2003 currently.
EE_NavigatorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

divyeshhdoshiCommented:
increase connection timeout of connection object.

When u are executing query then check it is in open state
if Yes 1) Execute query
if No 2) Reopen connection and execute query.

0
barfiCommented:
I found this at following link:(I hope it helps)

http://www.dba-oracle.com/t_connect_time_idle_expire_timeout.htmT

he sqlnet.ora inbound_connect_timeout parameter
The sqlnet.ora inbound_connect_timeout parameter is used to limit the time, set in seconds, for a client to connect with the database server and provide the required authentication information.

As we have all seen with recent worm and virus attacks, unauthorized access to a system service such as the Listener or database server can result in denial-of-service attacks. In a denial-of-service attack, an unauthorized client attempts to block the authorized users ability to access the system. Malicious clients or hackers may attempt to flood the Listener or database server with bogus connect requests solely to consume resources, such as connections, processes, or threads.

To minimize the effect of denial-of-service attacks, you should configure limits that constrain the time in which resources can be held prior to authentication. In this way, client attempts to exceed the configured limits will result in connection terminations and an audit trail containing the IP address of the client being logged.

To limit consumption of Oracle 10gs resources by unauthorized users and enable an audit trail, you should set time-limit values for the sqlnet.inbound_connect_timeout parameter described previously. (This parameter does not have default values.)

Bugs
Bug (2441734) which is port-specific to Windows where setting SQLNET.EXPIRE_TIME wastes stack memory reducing the total number of connections which can be achieved. It is fixed in Oracle10i and included in the 9.2.0.3 patchset release. The workaround is to set SQLNET.EXPIRE_TIME = 0 or remove it from sqlnet.ora

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.