Unanswered: RPC call leaves sessions open in the Remote end.
I have a distributed database application.
A RPC call leaves connections open on the remote end.
The RPC call is done via a application running at the host machine.
Though the response is received pretty quickly the connections remain open.
After some time the application hangs as more connections to the remote database is not possible.
1) What OS & OS version for all systems involved?
2) What versions of all Oracle DBs involved?
>After some time the application hangs as more connections to the remote database is not possible.
If application does "hang", what evidence do you have that it is due to having too many open connections?
Why doesn't "application" error out rather than "hang"?
>If I close and open the connection every time, will it not affect the performance?
It sounds to me that you already have "performance problems".
Which is better, slow & working or broken & not working?
What does "RPC" mean? (Remote Procedure Call?)
If so, exactly how does the remote database invoke the RCP?
Has this ever worked reliably?
Well both the Dbs are 8is.
Operating system Unix on Solaris. I will get back with more details later.
Well the application, a provisioning system, basically performs lots of other non database activities.
Sometimes data from external systems have to be accessed, We use PRo*C to make these oracle calls.
By RPC I mean ........ package.procedure@remotedatabase();
It used to work fine before, however , there has been a lot of traffic coming thru to the systems and a lots of call are being made at a particular time.