getting request timeout exceptions from a asp.net application using the Oracle client with multiple schemas -

We have an ASP.NET application that uses the Oracle client. In the connection string, we specify 3 basic attributes: Data source, user id, and password we are using connection pooling. Our data resides in 2 separate Oracle schemas. Most requests are for data from Schema 1. Data from Schema 2 is coming from time to time with callouts

Is it possible that the connections are linked to a schema?

This will be considered a lot since most calls are for data from Schema 1, so the pool is filled with connections that are good for schema 1 only. After that a call comes for data from schema 2 and any connection in the pool can not satisfy the request and we get timeout.

Thanks for any help - Greg

An Oracle Connection is always a schema Tied, the default user has its own schema. If you use two different connection strings, then you already have two different pools, so I suspect that it might be that you hit the maximum sessions for the database.

Compare your "Maximum Pool Size" setting to your "session" example parameter. The default I think is 100 for 11G, but you have not mentioned that version you may need to collide with processor, or reduce the size of Max Pool.

You should find out how many actual Oracle sessions are Username, calculation (1) Username from V $ session group;