Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you can use odac (odp) <strong>11g</strong>, you have setting Validate Connection for your pool. It can validate the connection before you use it. </p> <blockquote> <p>The <strong>Validate Connection</strong> attribute validates connections coming out of the pool. This attribute should be used only when absolutely necessary, because it causes a round-trip to the database to validate each connection immediately before it is provided to the application. If invalid connections are uncommon, developers can create their own event handler to retrieve and validate a new connection, rather than using the Validate Connection attribute. This generally provides better performance.</p> </blockquote> <p>If it will not be good enough - you can try <a href="http://docs.oracle.com/cd/E11882_01/win.112/e18754/featConnecting.htm#i1006393" rel="nofollow noreferrer">this</a> document from oracle.</p> <blockquote> <p>Connection Pool Management</p> <p>ODP.NET connection pool management provides explicit connection pool control to ODP.NET applications. Applications can explicitly clear connections in a connection pool.</p> <p>Using connection pool management, applications can do the following:</p> <p>Note: These APIs are not supported in a .NET stored procedure. Clear connections from connection pools using the <strong>ClearPool</strong> method.</p> <p>Clear connections in all the connection pools in an application domain, using the <strong>ClearAllPools</strong> method.</p> <p>When connections are cleared from a pool, ODP.NET repopulates the pool with new connections that have at least the number of connections set by Min Pool Size in the connection string. New connections do not necessarily mean the pool will have valid connections. For example, if the database server is down when ClearPool or ClearAllPools is called, ODP.NET creates new connections, but these connections are still invalid because they cannot connect to the database, even if the database comes up a later time.</p> <p>It is recommended that ClearPool and ClearAllPools not be called until the application can create valid connections back to the database. .NET developers can develop code that continuously checks whether or not a valid database connection can be created and calls ClearPool or ClearAllPools once this is true.</p> </blockquote> <p>Also, may be <a href="https://stackoverflow.com/questions/7845559/odp-net-connection-pooling-how-to-tell-if-a-connection-has-been-used">this post</a> will help you.</p> <p><strong>Update</strong>: As pointed by @MPelletier, for oracle 12 <a href="https://docs.oracle.com/database/121/ODPNT/featConnecting.htm#ODPNT174" rel="nofollow noreferrer">the link is different</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload