JDBC - Oracle Thin drv.

Hi, is there anybody who can tell me which version of JDBC can be supported by classes12_01.zip driver? Tnx a lot.

Similar Messages

Jdbc:oracle:thin:@[host]:[port]:[sid] problem:

Hi all
When I try to make connection through this string jdbc:oracle:thin:@localhost:1521:orcl , It failed to connect to the database.
I am trying to connect to database through obiee 11.1.1.5 by jdbc connectivity.
Please tell me its solution.....
Thanks
Rizwan Ali

Hi,
The TNSNAME.ora that the OBIEE11g uses is insede the folder <OBIEE11g_HOME>\Middleware_Home\Oracle_BI1\network\admin
(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = IP address)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = orcl)))
Refer
http://123obi.com/2011/03/error-the-connection-has-failed-in-obiee-11g/
http://gerardnico.com/wiki/database/oracle/connect_descriptor
FYI: OTN Message:
1. If you just need one TNS alias, then copy the database connection descriptor from database tnsnames.ora file to the tnsnames.ora file under the BIEE directory:
[middleware home]/[oracle home]/Oracle_BI1/network/admin
2. You may also copy the entire tnsnames.ora file
3. Another alternative is to set the TNS_ADMIN environment varaible which would point to the directory where a tnsnames.ora file is located. This would need to be set as a System Environment variable in Windows or in the command shell if starting from a command-line. For Unix/Linux, it would need to configured in the user profile that owns the software or set explicitly in the shell if starting from the command-line. See Note 111942.1 Setting TNS_ADMIN Environment Variable for more information on adding this environment variable.
Thanks
Deva

Connection reset using JDBC Oracle thin Driver (towards 10g DB)

Hi we have a home-grown application and a Oracle 10g (10.2.0.1) database.
We created a scheduled servlet that gets a JDBC connection from a persistent connected cache (an OracleDataSource object registered using OracleConnectionCacheManager). The servlet runs every 15 minutes and runs the query "SELECT SYSTIME FROM DUAL" on 10g Database as XYZ user. The datapool was created yday on web-app and all queries ran successfully for about 5 hours after which it reported a connection reset error.
I can then conclude that we cannot keep the server session alive for the JDBC client by running frequent SQL queries.
We didnt get any messages on the DB server side that indicate the release of the session
Ultimately, we are struggling with reset connections from our applications that are
using the JDBC thin oracle driver; after a couple of hours of idle
connections, we receive the below error from the JDBC driver:
Jul 5, 2007 10:59:53 AM oracle.jdbc.driver.DatabaseError throwSqlException
WARNING: DatabaseError.throwSqlException(e): Unable to find ORA number from
exception Jul 5, 2007 10:59:53 AM oracle.jdbc.driver.DatabaseError
findMessage
WARNING: DatabaseError.findMessage(errNum, obj): returned Io exception:
Connection reset Jul 5, 2007 10:59:53 AM
oracle.jdbc.driver.PhysicalConnection getWarnings
INFO: PhysicalConnection.getWarnings()
Any suggestions please ?
Vk

The code itself is fine; the problem is with one of:
1) the connection URL
2) intermediate networking
3) the database itself
1) your connection URL is "jdbc:oracle:thin:@127.0.0.1:1521:orcl"
- is Oracle really running on the default port, 1521
- is the installation SID really "orcl"
2) lots of possibilities, but only a couple are likely
- is TCP/IP configured and running on your host
- is there a persoanl firewall rpduct running? perhaps it's blocking the connection
3) Is Oracle running?
Is the listener running?

Jdbc:oracle:thin:@ service name too long

I am going to use jdbc:oracle:thin:@ as my connection.
but my service name is too long....
is that any ways to include the long service name?
Thanks!

user652882,
Pardon me for asking, but how do you know your service name is too long?
Good Luck,
Avi.

ATG CIM: Not able to connect to database jdbc:oracle:thin

Hi All,
I am trying to setup a ATG environment on windows boxes. Below is the setup:
VM1) DC - Windows Domain Controller (Windows Server 2008)
VM2) javadb - Oracle 11g (Windows Server 2008)
VM3) javaweb - ATG 10.0.3 / WebLogic wlserver_10.3/ TomCat 7 (Windows Server 2008)
Installation / Setup Progress
* Oracle 11g installation successful. Sample DB successfully created.
* WebLogic installation successful. Base_Domain successfully created.
* Able to create successful connection to Oracle (javadb vm) from TomCat (javaweb vm) and query data
Error: When configuring CIM I keep on getting >> "Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott"+_
Corrective action already taken:
1) Disabled firewall on all boxes
2) Added path of JDBC driver (ojdbc6.jar) in Environment Variables
3) Tested Oracle 11g (javadb vm) connectivity both from Eclipse and Tomcat. Which is successful
4) Cleared all files under C:\ATG\ATG10.0.3\CIM\data to reset CIM
Please refer CIM details below:
===========================================
CIM DISPLAY START
===========================================
-------ENTER CONNECTION DETAILS-----------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
Select Database Type
*[1] Oracle Thin
[2] MS SQL
[3] iNet MS SQL
[4] DB2
[5] My SQL
Select one > 1
Enter User Name [[system]] > scott
Enter Password [[**********]] > **********
Re-enter Password > **********
Enter Host Name [[javadb]] > javadb
Enter Port Number [[1521]] > 1521
Enter Database Name [[sampledb]] > SampleDB
Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
>
Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]]
Enter JNDI Name [[ATGProductionDS]] >
-------CONFIGURE DATASOURCE PRODUCTION CORE-----------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
[C] Connection Details - Done
*[T] Test Connection
[S] Create Schema
Import Initial Data
[D] Drop Schema
[O] Configure Another Datasource
> T
-------TEST DATASOURCE CONNECTION---------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
>> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott
===========================================
CIM DISPLAY END
===========================================
===========================================
CIM LOG START
===========================================
**** Warning     Mon Jul 23 22:46:25 IST 2012     1343063785645     atg.cim.worker.status.StatusUpdateValidator     Status id nonswitchingCore-DatasourceConnectionTemplateStep is unknown.
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB : -1     java.lang.ArrayIndexOutOfBoundsException: -1
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.setSessionFields(T4CTTIoauthenticate.java:948)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.<init>(T4CTTIoauthenticate.java:225)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:358)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:538)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:582)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:185)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:526)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:588)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getConnection(BasicDataSource.java:475)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.FakeXADataSource.getXAConnection(FakeXADataSource.java:671)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.createResource(MonitoredDataSource.java:837)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.populateSlot(ResourcePool.java:2064)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.checkOut(ResourcePool.java:1332)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.co(MonitoredDataSource.java:1792)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.getConnection(MonitoredDataSource.java:1070)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.performTestConnection(TestJdbcConnectionValidator.java:319)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.validate(TestJdbcConnectionValidator.java:266)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.executeValidations(StepExecutor.java:280)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.text.TextDisplay.processStep(TextDisplay.java:338)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.UIDispatchImpl.processStep(UIDispatchImpl.java:89)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:201)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:73)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:216)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:69)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:78)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.startCimFlow(Launcher.java:168)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.main(Launcher.java:68)
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator
**** Error     Mon Jul 23 22:46:32 IST 2012     1343063792218     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Error initializing connection from parameters. Test for jdbc connection failed
===========================================
CIM LOG END
===========================================
Any suggestion how to resolve this issue. Thanks in advance.
cheers,
Sandeep
Edited by: 948180 on Jul 23, 2012 11:29 PM

Hi,
Earlier my ojdbc6.jar path was not at the beginning of ClassPath. I have made necessary changes. Please refer below:
Environment Variables Settings on machine where CIM resides:
PATH = C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar+;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Java\jre7\bin;C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin;C:\Program Files\cvsnt;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Sun\JavaDB\bin;C:\Program Files\Sun\JavaDB\lib;;C:\ATG\ATG10.0.3\MySQL\win32\bin;C:\ATG\ATG10.0.3\home\bin\;C:\Oracle\Middleware\wlserver_10.3\server\lib\;
Note: I have verified by ojdbc6.jar path.
Below are the precise steps I executed after updating my environment variables and restarting CMD.
===========================================
CIM DISPLAY START
===========================================
C:\ATG\ATG10.0.3\home\bin>cim.bat
Nucleus running
_ | () |
__ _ | |_ __ _ ----
/ _` | | __| / _` |
| (_| | | |_ | (_| |
\__,_| \__| \__, |
|___/
Configuration Installation Manager
=======CIM MAIN MENU============================================================
enter [h]elp, [q]uit to exit
Choose the task you want to perform:
*[1] Database Configuration
[2] Server Instance Configuration
[3] Application Assembly & Deployment
[P] Product Selection - Done (ATG B2C Commerce)
[A] Select Application Server - Done (Weblogic Online)
[C] Custom CIM Plugin Launcher
> 1
-------CALCULATE DATASOURCE DEPENDENCIES----------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Calculating Datasource Dependencies. View log file at C:/ATG/ATG10.0.3/home/
../CIM/log/cim.log
|. . |
|. . |
-------SELECT A DATASOURCE TO CONFIGURE-----------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
*[P] Publishing
[C] Production Core
[D] Done
> c
-------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
[C] Connection Details - Done
*[T] Test Connection
[S] Create Schema
Import Initial Data
[D] Drop Schema
[O] Configure Another Datasource
> t
-------TEST DATASOURCE CONNECTION-----------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
>> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
scott
*[E] Edit Connection Details
[R] Redo
[D] Done
> e
-------RE-USE VALUES FROM PREVIOUS DATASOURCE-----------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
Base on previous database details:
[1] system@jdbc:oracle:thin:@javadb:1521:sampledb
[2] scott@jdbc:oracle:thin:@javadb:1521:SampleDB
*[3] None/Use Existing
Select one > 2
-------ENTER CONNECTION DETAILS-------------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
Select Database Type
*[1] Oracle Thin
[2] MS SQL
[3] iNet MS SQL
[4] DB2
[5] My SQL
Select one > 1
Enter User Name [[scott]] > scott
Enter Password [[**********]] > **********
Re-enter Password > **********
Enter Host Name [[javadb]] > javadb
Enter Port Number [[1521]] > 1521
Enter Database Name [[SampleDB]] > SampleDB
Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
> jdbc:oracle:thin:@javadb:1521:SampleDB
Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]
] > C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar
Enter JNDI Name [[ATGProductionDS]] > ATGProductionDS
-------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
[C] Connection Details - Done
*[T] Test Connection
[S] Create Schema
[I] Import Initial Data
[D] Drop Schema
[O] Configure Another Datasource
> T
-------TEST DATASOURCE CONNECTION-----------------------------------------------
enter [h]elp, [m]ain menu, [q]uit to exit
Production Core
>> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
scott
*[E] Edit Connection Details
[R] Redo
[D] Done
>
===========================================
CIM DISPLAY END
===========================================
Don't understand what could possibly be going wrong.
Cheers,
Sandeep
Edited by: 948180 on Jul 24, 2012 12:23 AM

How to set a sql query time out with jdbc:oracle:thin

should i change the JDBC driver with jdbc:oralce:XA:thin or other driver with XA?

SQL query timeout may be set with setQueryTimeout.
http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#setQueryTimeout(int)
A query timeout bug is fixed in Oracle JDBC Drivers release
10.1.0.2.0 (10g)
FIXED BUG-2249191
In the Server Internal Driver, setting the query timeout does not
+(and likely will never) work. The query execution will not be+
canceled when the timeout expires, even if the query runs forever.
Further, after the query returns, the execution of your code
may pause for the length of the timeout.
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_readme101020.html

CallableStatement does not run PL/SQL with jdbc:oracle:thin driver

I have a very simple PL/SQL function:
FUNCTION CalculateDistance
(x1 IN NUMBER, y1 IN NUMBER, x2 IN NUMBER, y2 IN NUMBER)
RETURN NUMBER
AS
distance NUMBER;
BEGIN
distance := SQRT(POWER(x1-x2,2) + POWER(y1-y2,2));
return distance;
END;
I call it with:
CallableStatement cs = null;
try {
biomassStatement = con.prepareCall("{ call MYPACKAGE.CalculateDistance(?, ?, ?, ?, ?)}");
cs.setDouble("X1", -367546.78402892);
cs.setDouble("Y1", 150712.8161204);
cs.setDouble("X2", -2155095.49289);
cs.setDouble("Y2", 774013.149084);
cs.registerOutParameter("v_Return", OracleTypes.NUMBER);
cs.execute();
The only answer I get is:
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'CALCULATEDISTANCE'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
I tried it with different Data sources (common, pool, XA) and nothing works...
Tried using ojdbc14_g.jar to see if could get more information with no help...
HELP!!!

Hi,
You are calling a FUNCTION, i.e you have one return value (And four arguments)
So according to javadocs
http://download.oracle.com/javase/6/docs/api/java/sql/CallableStatement.html
Your synbtax should be like:
{?= call <procedure-name>[(<arg1>,<arg2>, ...)]}Rigtht now, your call seems to be for a procedure having five arguments.
Regards
Peter

Jdbc oracle jdbc-thin driver subname

I am working on Windows 2000 environment, using oracle8i 8.1.7 JDBC-Thin driver for use with JDK 1.2.x. The oralce8i 8.1.7 database is on another linux box. I can access the linux box through its ip address, but not by its hostname since it's not accessiable by the dns server. In my code, in the JDBCUrl, I used ip address instead of the hostname, e.g. "jdbc:oracle:thin:@10.0.113.108:1521:ora1". But I got the error like: "java.sql.SQLException: Io exception: The Network Adapter could not establish the connection". If I add a entry in my working machine's hosts file to map the hostname, I can fix the problem. But I don't know if this is the solution, or there is other better solutions.
Thanks
null

Using a hosts file entry is a common solution for problem where the dns lookup does not contain an entry for a RDBMS server platform.
The real solution is to resolve this issue :
"where the dns lookup does not contain an entry for a RDBMS server platform."

JDBC logging disabled with Oracle thin driver

Hi,
I am trying to turn on JDBC logging through the weblogic console application (WL
6.1 with CMP). In the jdbc log file I do not see the SQL statments.
It looks like logging is somehow disabled (check one of the logs statements below)
by some means. Any ideas, I am making use of oracle thin driver.
Thanks
Mohit
Following log messages are generated!!!!!!
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DRVR OPER Disabled logging
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing

Mohit,
Remove oracle/jdbc/driver/OracleLog from classes12.zip, and it should
work (it needs to pick up only this class from weblogic.jar).
Paul
Hi,
I am trying to turn on JDBC logging through the weblogic console application (WL
6.1 with CMP). In the jdbc log file I do not see the SQL statments.
It looks like logging is somehow disabled (check one of the logs statements below)
by some means. Any ideas, I am making use of oracle thin driver.
Thanks
Mohit
Following log messages are generated!!!!!!
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DriverManager.getDriver("jdbc:oracle:thin:@(description=(address=(host=192.168.161.120)(protocol=tcp)(port=1521))(connect_data=(sid=DOPERS01)))")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@4301c9]
DRVR OPER Disabled logging
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@13eb9c]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@4f83d1]
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 Statement.setEscapeProcessing
DRVR DBG1 doDefaultTypes
DRVR DBG1 doDefinesFromTypes
DRVR DBG1 ResultSet.getMetaData
DRVR DBG1 Statement.setEscapeProcessing

Web Logic 6.1 JDBC Pooling with the Oracle Thin Driver

Hi,
We're slowly getting through a WebLogic 4.5.1 to 6.1 conversion for a small application
at my company. Initially, we had trouble getting the Oracle thin driver working.
We've finally cracked this nut. Now we're trying to get pooling working, and
cannot find an example of doing this with the Oracle thin driver.
Would anyone be able to provide:
1. the portion of the config.xml that pertains to building a connection pool using
the Oracle thin driver
2. the two lines of code for loading the driver and getting a connection from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Thanks very much!
Jeff Ryan
The Hartford

"Jeff Ryan" <[email protected]> wrote:
>
1. the portion of the config.xml that pertains to building a connection
pool using
the Oracle thin driver
You don't usually edit the config.xml unless it is absolutely necessar. Instead,
you can config the pool in the GUI admin console, quite easily. After you successfully
configed the pool in the console, it is written into the config.xml file for you.
Only thing special when config the pool is the name of the driver and the url.
url: jdbc:oracle:thin@dbhost:dbport:dbinstance
driver: oracle.jdbc.driver.OracleDriver
If you prefer, you can also config the pool from the command line. It is detailed
in the "Weblogic Server Command-line Interface Reference".
2. the two lines of code for loading the driver and getting a connection
from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Again, you don't use the connection directly. Instead, you use "Data Source".
Data source in weblogic is just a connection object factory associated with a
JNDI name. You can therefore lookup the data source with the JNDI name and from
the data source object, you get the connectin object. No need to explicitly load
the driver class.
There are plenty of example codes available in the weblogic examples installed
with 6.1, that uses the data source.
Charles

Jdbc connection using oracle thin driver( using jdk1.4 and oracle8 )

hello ..
while i was tring to connection using oracle thin driver and jdk1.4 am getting the below error message. i have set the class path for the driver also. am using oracle8 personal edition and jdk1.4.
[java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
        at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
        at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
        at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
        at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
        at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:468)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
        at java.sql.DriverManager.getConnection(DriverManager.java:512)
        at java.sql.DriverManager.getConnection(DriverManager.java:171)
        at Connexa.main(Connexa.java:18)[/b]
Press any key to continue...
my program is....
import java.sql.*;
import java.io.*;
import java.util.*;
import oracle.jdbc.driver.*;
// needed for new BFILE class
import oracle.sql.*;
   public class Connexa {
public static void main (String args []) throws Exception {
        Statement stmt=null;
try{
    // Load the Oracle JDBC driver
    //DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Class.forName("oracle.jdbc.driver.OracleDriver");
    // Connect to the database
    // You can put a database name after the @ sign in the connection URL.
Connection conn =
DriverManager.getConnection("jdbc:oracle:thin:@127.0.0.1:1521:orcl","scott","tiger");
    //Connection conn =
    // DriverManager.getConnection ("jdbc:odbc:datasource", "system", "manager");
    stmt = conn.createStatement ();
catch (SQLException e)
      e.printStackTrace();

The code itself is fine; the problem is with one of:
1) the connection URL
2) intermediate networking
3) the database itself
1) your connection URL is "jdbc:oracle:thin:@127.0.0.1:1521:orcl"
- is Oracle really running on the default port, 1521
- is the installation SID really "orcl"
2) lots of possibilities, but only a couple are likely
- is TCP/IP configured and running on your host
- is there a persoanl firewall rpduct running? perhaps it's blocking the connection
3) Is Oracle running?
Is the listener running?

Database connection encryption and integrity with ColdFusion and Oracle thin client

As ColdFusion datasource we are using the Oracle thin client to connect with the database. So, basically we are using a JDBC URL such as jdbc:oracle:thin:@... and as Driver Class oracle.jdbc.OracleDriver. This works successfully however we would like to set encryption and integrity parameters as well. In Java this is done similarly by setting a Properties object prior to getting a connection as follows:
Properties prop = new Properties();
prop.put("oracle.net.encryption_client", "REQUIRED");
prop.put("oracle.net.encryption_types_client", "( DES40 )");
prop.put("oracle.net.crypto_checksum_client", "REQUESTED");
prop.put("oracle.net.crypto_checksum_types_client", "( MD5 )");
OracleDataSource ods = new OracleDataSource();
ods.setProperties(prop);
ods.setURL("jdbc:oracle:thin:@localhost:1521:main");
Connection conn = ods.getConnection();
Is there a way that I can pass these parameters to the ColdFusion datasource. Ideally, I would love to do this centrally in such way that a change to all the cfquery or cfstoredproc is not needed.
I also know that in application servers such as Oracle AS there is an option when creating a datasource which says "Add Properties". In there you can add such properties. So, I was thinking of maybe creating a JNDI DS in the app. server and then magically connecting to it but this may have some impacts on the app.
Besides this I was also thinking of communicating with the CF datasource through the CF admin API (cfide.adminapi.administrator) and also the option of extending the Oracle driver so that when CF connects with it these params are already set.
I would love to have your professional opinion and suggestions on this.

I believe the thin driver actually needs the IP address (not the DNS name). Also, is "java" the name of the Oracle instance to which you are trying to connect?
Try the following:String driver = "jdbc:oracle:thin";
String dbIP = "W2RZ1NXG01's IP address";
String dbPort = "1530";
String dbSid = "java";
String dbUser = "Admin";
String dbPswd = "apassword";
String cnctStr = driver + ":@" + dbIP + ":" + port + ":" + dbSid;
try
    Class.forName("oracle.jdbc.driver.OracleDriver");
    con = DriverManager.getConnection( cnctStr, dbUser, dbPswd );
    stmt = con.createStatement();
    stmt.executeUpdate(createString);
    stmt.close();
    con.close();
catch(SQLException ex)
    System.err.println( "The following SQLException occurred: " + ex );
    System.err.println( "Message: " + ex.getMessage() );

Any ideas on a MS Jet Access Error on Oracle Thin Driver?

I am getting the following error when attempting to connect to an Oracle 8i database on a UNIX server from a servlet on an NT server using Jrun:
Error
java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot find the input table or query 'EMPLOYEE'. Make sure it exists and that its name is spelled correctly.
Where could this come from since I am importing the Oracle classes and have the JRun and system classpath set to where classes12.jar is located. There are no ODBC DSN settings for this DB on the server.
I am using this syntax to get the connection:
Class.forName("oracle.jdbc.driver.OracleDriver");
conn = DriverManager.getConnection(
"jdbc:oracle:thin:@10.20.10.112:1521:databasename",
"username",
"password");

it seems like the connection is being made successfully, otherwise you would get a different error.
Maybe your SQL has to be case sensitive in relation to the tablename??

Can't create connection pool using weblogic 6.1 with Oracle thin driver

Hi !
I have tried to create a connection pool from adminconsole. My CLASSPATH setting
is as follows :
F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
D:\Oracle\Ora81\jdbc\lib\classes12.zip;
D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
D:\Oracle\Ora81\jdbc\lib\classes111.zip;
F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
D:\Oracle\Ora81\lib;
F:\ant\jakarta-ant1.\bin;
E:\weblogic\oci\classes;
E:\weblogic\oci\classes\weblogic\xml\license;
E:\weblogic\oci\license;
E:\bea\wlserver6.1\lib;
E:\PetStoreHome\petstore1.3;
Following is the configuration.
#Oracle thin driver Method #2
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
     initialCapacity=4,\
     maxCapacity=10,\
     capacityIncrement=1,\
     props=user=xxx;password=xxx;server=test
#Add a TXDataSource for the connection pool:
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
# Add an ACL for the connection pool:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
I did append the file weblogic.properties with the above config. Now when I start
the Weblogic server I get the following error :
Starting WebLogic Server ....
<Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading configuration file
.\config\petstore\config.xml ...>
<Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Admin
Server "petstoreServer" for domain "petstore">
<Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting discovery of Manag
ed Server... This feature is on by default, you may turn this off by passing -Dw
eblogic.management.discover=false>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB) can't be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB) can't be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB) can't be
cr
eated with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin) can't be
created with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application Poller not star
ted for production server.>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the WebLogic Server
Tour running on this server. If your browser fails to
launch, point your browser to the URL
"http://burtsun:7001"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "petstoreServer" for domain "petstore" running in Production Mode>
Could anyone please help me ?
Thanks
..Madhuri

Madhuri wrote:
>
Hi Joe !
I didn't get what you would like to point out. Actully, I am using same config.,
but not to disclose the info. I gave you @test and username/password xxx/xxx.Ok. Now, assuming your pool looks like what I showed, the issue is probably
that there are multiple Oracle driver zips around, and your standlaone program
is using a different, newer, better one than the server. Our weblogic jar files
include a classes12.zip Oracle thin driver, but there are multiple versions of
classes12.zip, and the latest from oracle is better than the one we sealed into
our packaging. Please use jave -verbose to identify exactly which Oracle sip file
you are using in the successful case, then make sure this zip file comes before
any weblogic stuff in your weblogic server's classpath, so we'll use the same
driver. This should work. Edit the script you sue to start weblogic to verify
the classpath does end up with the oracle driver ahead of all weblogic stuff.
Joe
>
Please let me know.
Thanks
.Madhuri
Joseph Weinstein <[email protected]> wrote:
Madhuri wrote:
Hi Joe !
Here is the sample java code. Please let me know how I can test thisin weblogic
6.1.
Thanks
.MadhuriWell fine! That was easy. Your pool definition didn't have the same URL
or
user or password as this code. Try this for your pool definition:
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@adl-gbsdevel:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=10,\
maxCapacity=10,\
capacityIncrement=1,\
testConnsOnReserve=true,\
testTable=dual,\
props=user=mkelkar;password=mkelkar
Let me know,,,
Joe
Joseph Weinstein <[email protected]> wrote:
The key is in the log:
Could not create pool connection.
The DBMS driver exception was:
java.sql.SQLException: invalid arguments in call
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
Now we need to simplify the problem. Please make a simple 15-line
standalone
Java program like you'd find with the Oracle driver's examples, with
no
weblogic code in the picture. Just make a JDBC connection using Oracle's
driver, and show me that code. Then I can translate that into a pool
definition.
Joe
Madhuri wrote:
Hi Joe !
Thanks for your prompt reply. I tried the way you suggested but
it
still it gives
me the same error. I am attching here the weblogic.log file.
Thanks again
..Madhuri
Joseph Weinstein <[email protected]> wrote:
We'd want to see the log during booting, where the pool
is being created to see why that failed. Try a pool
definition with no blank lines, no whitespace at the
end of lines, and no server property. The thin driver
doesn't like that:
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=4,\
maxCapacity=10,\
capacityIncrement=1,\
props=user=xxx;password=xxx
Joe
Madhuri wrote:
Hi !
I have tried to create a connection pool from adminconsole. My
CLASSPATH
setting
is as follows :
F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
D:\Oracle\Ora81\jdbc\lib\classes12.zip;
D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
D:\Oracle\Ora81\jdbc\lib\classes111.zip;
F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
D:\Oracle\Ora81\lib;
F:\ant\jakarta-ant1.\bin;
E:\weblogic\oci\classes;
E:\weblogic\oci\classes\weblogic\xml\license;
E:\weblogic\oci\license;
E:\bea\wlserver6.1\lib;
E:\PetStoreHome\petstore1.3;
Following is the configuration.
#Oracle thin driver Method #2
weblogic.jdbc.connectionPool.thin=\
url=jdbc:oracle:thin:@test:1521:PROJECT,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=4,\
maxCapacity=10,\
capacityIncrement=1,\
props=user=xxx;password=xxx;server=test
#Add a TXDataSource for the connection pool:
weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
# Add an ACL for the connection pool:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
I did append the file weblogic.properties with the above config.
Now
when I start
the Weblogic server I get the following error :
Starting WebLogic Server ....
<Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading
configuration
file
\config\petstore\config.xml ...>
<Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting
WebLogic
Admin
Server "petstoreServer" for domain "petstore">
<Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting
discovery
of Manag
ed Server... This feature is on by default, you may turn this
off
by
passing -Dw
eblogic.management.discover=false>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB)
can't
be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB)
can't
be creat
ed with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB)can't be
cr
eated with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
Source
creation:
weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin)can't be
created with non-existent Pool (connection or multi) (thin)>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application
Poller
not star
ted for production server.>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
After the server has booted, your browser should
automatically launch and point to the WebLogic Server
Tour running on this server. If your browser fails to
launch, point your browser to the URL
"http://burtsun:7001"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThreadlistening
on port 7001>
<Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
ng on port 7002>
<Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started
WebLogic
Admin
Server "petstoreServer" for domain "petstore" running in ProductionMode>
Could anyone please help me ?
Thanks
..Madhuri
Name: weblogic.log
weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
Encoding: base64
Name: PrintColumns.java
PrintColumns.java Type: Visual Cafe File (application/x-unknown-content-type-VisualCafeFile.Document)
Encoding: base64

How to specify JDBC Oracle url using deployment tool - Entity Bean

Hello I'am new to EJB.
When creating a entity bean-managed persistence and you need to specify the jdbc url with user name
and password to establish a connection object, how does one specify that in the deployment
tool?
Heres an example of what has in the J2EE tutorial has in AccountEJB to get an connection object
private String dbName = "java:comp/env/jdbc/AccountDB";
private void makeConnection() throws NamingException, SQLException {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup(dbName);
con = ds.getConnection();
Now if my oracle jdbc url is to be jdbc:oracle:thin:@Abe:1521:dev
ie My host is Abe, port number 1521 and database name of dev and username/password will be system/manager.
what would my dbName be at the top?
Would my JNDI lookup of a DataSource resource "java:comp/env/jdbc/AccountDB" become "java:comp/env/jdbc/dev" for starters?
In the Resource Factories Reference Code I've add a reference of
Coded Name: jdbc/dev
Type: javax.sql.DataSource
Authentication: Container
and down the bottom of the I've put JNDI Name: MyAccount
according to the AccountClient code of:
Context initial = new InitialContext();
Object objref = initial.lookup("MyAccount");
and put User Name of "system" and Password of "manager"
I'am sure in the source code I have to put
Class.forName("oracle.jdbc.driver.OracleDriver")
else you would get that no sutitable driver error, maybe you don't have to if ejb server is smart enough?
What I'am confuse about is where to specify the jdbc url of "jdbc:oracle:thin:@Abe:1521:dev" ??
Know it won't work because of this vital part. Do you have to put that somewhere else in the deployment tool or properties file, or some other tool??
Please help
Thanks
Abraham Khalil

When running the client after successful deployment with jdbc, I'am getting
javax.naming.CommunicationException: java.rmi.MarshalException: CORBA MARSHAL 1398079699 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : minor code: 1398079699 completed: Maybe
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : minor code: 1398079699 completed: Maybe
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(CDRInputStream_1_0.java:923)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(CDRInputStream.java:281)
at com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(TCUtility.java:274)
at com.sun.corba.ee.internal.corba.AnyImpl.read_value(AnyImpl.java:554)
at com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(CDRInputStream_1_0.java:605)
at com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(CDRInputStream.java:252)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Util.java:203)
at javax.rmi.CORBA.Util.readAny(Unknown Source)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:133)
at javax.naming.InitialContext.lookup(Unknown Source)
at AccountClient.main(AccountClient.java:21)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:151)
at javax.naming.InitialContext.lookup(Unknown Source)
at AccountClient.main(AccountClient.java:21)
One thing I don't like about EJB is that everything is transparent which is good! But its much
harder to debug! :( Tried to see if I can figure it out. Hope someone has seen this problem before?

JDBC - Oracle Thin drv.

Similar Messages

Maybe you are looking for