Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JDBC connection pool creation error.

20 views
Skip to first unread message

Vivek Raikanti

unread,
Oct 17, 2002, 4:20:48 PM10/17/02
to
Hello There,
I get the below mentioned stack trace when a jdbc connection pool is being
created.
I'm not sure what "explicit attach" is ? ( mentioned in the SQL exception)
I'm using Weblogic 6.1 with Weblogic's Jdriver for Oracle . ( oci901_8).
Also, my Oracle Client and Server version is 9.2.0.1 release 2.

As I'm not using the same version of the driver as the Oracle Server is,
would that be a problem ?

Thanks a lot in advance!
-Vivek

****************************************************************************
***********

Enter password to boot WebLogic server:
Starting WebLogic Server ....
<Oct 17, 2002 1:00:56 PM PDT> <Notice> <Management> <Loading configuration
file .\config\brgdomain\config.xml ...>
<Oct 17, 2002 1:00:59 PM PDT> <Notice> <WebLogicServer> <Starting WebLogic
Admin Server "brgserver1" for domain "brgdomain">
Starting Loading jDriver/Oracle .....


---------- LOGIN ERROR CODE: 24327


---------- LOGIN ERROR CODE: 24327
<Oct 17, 2002 1:01:10 PM PDT> <Error> <JDBC> <Cannot startup connection pool
"oraclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-24327: need explicit attach before authenticating
a user - (fnwa/********@discovery)
at
weblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
EnvFactory.java:193)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
EnvFactory.java:134)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:705)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650
)
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy27.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy35.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)

at
weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
EnvFactory.java:209)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
EnvFactory.java:134)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:705)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650
)
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy27.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy35.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
<Oct 17, 2002 1:01:10 PM PDT> <Error> <JDBC> <Error during Data Source
creation: weblogic.common.ResourceException: Data
Source(mondial-datasource-oraclePool) can't be created with non-existent
Pool (connection or multi) (oraclePool)>
<Oct 17, 2002 1:01:10 PM PDT> <Notice> <Management> <Application Poller not
started for production server.>
<Oct 17, 2002 1:01:10 PM PDT> <Notice> <WebLogicServer> <ListenThread
listening on port 7001>
<Oct 17, 2002 1:01:10 PM PDT> <Notice> <WebLogicServer> <SSLListenThread
listening on port 7002>
<Oct 17, 2002 1:01:11 PM PDT> <Notice> <Management> <Starting discovery of
Managed Server... This feature is on by defau
lt, you may turn this off by passing -Dweblogic.management.discover=false>
<Oct 17, 2002 1:01:11 PM PDT> <Notice> <WebLogicServer> <Started WebLogic
Admin Server "brgserver1" for domain "brgdomai
n" running in Production Mode>

****************************************************************************
*******************


Deepak Vohra

unread,
Oct 17, 2002, 7:41:55 PM10/17/02
to

Vivek Raikanti

unread,
Oct 17, 2002, 9:12:37 PM10/17/02
to
I have gone through the steps as mentioned in the below link ( at the Bea
Support Group website's FAQ ) and was able to connect using the utils.dbping
utility.
The command I used was,
" utils.dbping oracle fnwa fnwa MONDIAL_10.0.1.230 "
where "MONDIAL_10.0.1.230" is my TNS hoststring alias.


But when I try to run Weblogic using the below mentioned connection pool
configuration,

<JDBCConnectionPool CapacityIncrement="5"
DriverName="weblogic.jdbc.oci.Driver" InitialCapacity="5"
MaxCapacity="25" Name="oraclePool" Password="{3DES}WNPEbGZNtKc="
Properties="verbose=true;user=fnwa;server=MONDIAL_10.0.1.230"
Targets="brgserver1" URL="jdbc:weblogic:oracle"/>


it still doesnt work. It gives me the same below mentioned error message.
Could somebody tell me where I'm making the mistake ?


-Vivek

"Deepak Vohra" <dvoh...@sympatico.ca> wrote in message
news:3DAF4AC3...@sympatico.ca...
>
http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.js
p&event=link.view_answer_page_solution&answerpage=solution&page=wls/S-08804.


html
>
> Vivek Raikanti wrote:
>
> > Hello There,
> > I get the below mentioned stack trace when a jdbc connection pool is
being
> > created.
> > I'm not sure what "explicit attach" is ? ( mentioned in the SQL
exception)
> > I'm using Weblogic 6.1 with Weblogic's Jdriver for Oracle .

Mitesh Patel

unread,
Oct 18, 2002, 10:44:28 AM10/18/02
to Vivek Raikanti
Hi Vivek!
We have not certified 920 driver yet. As, you are using 920 client and 920
database, you need to use 920 jDriver. As you are using 901 weblogic jDriver,
you should use 901 client and not 920 client. However, you can use oracle 920
thin driver for creating connection pool instead using weblogic's 901 jDriver.
Mitesh

Vivek Raikanti

unread,
Oct 18, 2002, 8:30:23 PM10/18/02
to
Hi Mitesh,
As per your suggestion I have used Oracle's 9.2.0 Thin driver and tried
connecting to the database ( 9.2.0).
The dbping utility works correctly and says it is successful.
But when I try the query a table with a SELECT stmt, it comes back with the
below mentioned error.
My table is a one column entry with some string names. So there is no wrong
data in the table.
Am I missing something ?


Thanks for your help!

-Vivek


****************************************************************************
*****
Error encountered:

java.sql.SQLException: ORA-00911: invalid character

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
at
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
at
oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:2672)
at
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
at utils.dbping1.main(dbping1.java:113)


****************************************************************************
******


"Mitesh Patel" <Mitesh...@bea.com> wrote in message
news:3DB01E4C...@bea.com...


> Hi Vivek!
> We have not certified 920 driver yet. As, you are using 920 client and 920
> database, you need to use 920 jDriver. As you are using 901 weblogic
jDriver,
> you should use 901 client and not 920 client. However, you can use oracle
920
> thin driver for creating connection pool instead using weblogic's 901
jDriver.
> Mitesh
>
> Vivek Raikanti wrote:
>
> > Hello There,
> > I get the below mentioned stack trace when a jdbc connection pool is
being
> > created.
> > I'm not sure what "explicit attach" is ? ( mentioned in the SQL
exception)
> > I'm using Weblogic 6.1 with Weblogic's Jdriver for Oracle .

Vivek Raikanti

unread,
Oct 20, 2002, 4:10:28 PM10/20/02
to
Never mind!
solved it.. The stupid semicolon after the SELECT stmt caused the
"java.sql.SQLException: ORA-00911: invalid character"
exception.

Thanks anyway!

-Vivek

"Vivek Raikanti" <v...@decisiondesign.com> wrote in message
news:3db0...@newsgroups.bea.com...

0 new messages