Re: Oracle/ODBC and TP monitor

John Moriarty wrote:
>
> In an Oracle environment with ODBC running on the client how does
> Oracle handle the situation of several hundred clients connected
> to it at the same time? It would seem to be an awful lot of
> SQL*Net sessions running on a server. Do they have a concept
> of a Transaction Process Monitor or something like it? Do they
> suggest something else?

Regardless of ODBC, you can only talk to a remote Oracle7 server through SQL*Net. You are correct that several hundred sessions may be going into an Oracle server. However, if you are running the multithreaded server you will not have several hundred SQL*Net server processes running at the listener.

In such cases, the Oracle7 server is functioning as the transaction process monitor for the purpose of supporting distributed updates on that server. Each other server autonomously handles the distributed updates on its own databases. There is such as thing as the commit point. This is the server which has the final say on committing or rolling back then entire distributed update, but, effectively, each server is autonomous.

Oracle7 can coexist with several TPM technologies such as Encina, Tuxedo, etc. Oracle’s XA library provides the software hooks required to tightly couple Oracle7 applications to X/Open Distributed Transaction Processing (DTP) XA interface compliant technologies. To use the library, applications are built using Oracle’s Call Interface (OCI).

Hope this helps.

-- 
Hugo Toledo, Jr.   Author of "Oracle Networking" from Oracle Press
312.951.8012               Oracle WebSystem - Oracle Mobile Agents
mailto:hugo_at_mcs.com      Oracle Power Objects - Windows - Unix - C
http://www.mcs.com/~hugo/oracle.html        CompuServe: 72700,1705