ORA-24327 with OCI driver

Question

Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannot have
an initial connection pool size greater than 249. On the 250th one, there is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction and we've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-Vincent

Answer 1

Vincent Massol wrote:
>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Vincent,
Just for curiosity sake, what are you doing with 250 connections?
It's not in the Cactus area, is it? :-)
grin ;-)
No, I'm currently working for a customer, doing some lab performance tests.
We wanted to use the OCI driver for the TAF feature of OPS (transparent
application failover) but found that the Thin driver is performing so much
better that we have switched to using it along with the multipool feature of
WebLogic. Hi. Beware of 'TAF'. Note that all cursors will be defunct on failover,
so any JDBC statement or ResultSet in progress at the time of failover will
be lost. (IE: not at all transparent).
Joe
We haven't done any failover test yet so we don't know yet how the
multipool (with a 'load-balancing' strategy) perform upon failover of one
instance. If it's ok we'll keep using the thin driver. If not, we'll switch
back to OCI drivers and try the TAF feature.
Also, I don't think we really need that big number of connections. It seems
we had some other performance issue which the DB which was making us use
lots of connections on the WL side. With the thin driver we're only using
about 39-100 connections maximum with a thread count of 40 (that's because a
given message does up to 3 SQL statements per transaction (and a connection
is only effectively released in the pool after the commit)).
I've introduced Cactus on the project, of course, but only for the unit
tests (I'm also using Mock Objects) ... :-)
Regards,
-Vincent
Regards,
Slava Imeshev
"Vincent Massol" <[email protected]> wrote in message
news:[email protected]...
Hi,
We noticed that when we use the OCI driver for Oracle 8.1.7, we cannothave
an initial connection pool size greater than 249. On the 250th one,
there
is
a DBMS exception (ORA-24327) and weblogic says that it cannot create the
connection.
If we move to the Thin driver, there is no longer this restriction andwe've
tried it with success with more than 550 connections.
Anyone know any limitation about the OCI driver and if there is any
parameter on the OCI driver side or on the DB side to tune so that we
can
have more than 249 connections in our pool ?
FI, we have the following configuration (in config.xml) :
<JDBCConnectionPool CapacityIncrement="5"
Name="imJDBCConnectionPool" Targets="imadmin"
DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
InitialCapacity="270" MaxCapacity="270"
TestTableName="dual" RefreshMinutes="40"
ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
Properties="user=im;password=im;server=im09"/>
and we have the following TNSNAMES.ORA :
IM09.IM =
(DESCRIPTION =
(failover = on)
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
(CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
and SQLNET.ORA (to resolve the IM domain name) :
NAMES.DEFAULT_DOMAIN=IM
Thanks
-Vincent
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX