JDBC Driver Upgrade

Hi,
I need to update the JDBC driver in Portal server.
Can any body explain me as to what are the steps involved and where we can find the JDBC driver.
Thanks & Regards,
Vijith

Hi Vijith,
This thread may help you out
Updating JDBC Drivers
Regards
Radhika Kuthiala

Similar Messages

Override JDBC driver in 9.0.4 only for a specific application

Hi,
on of our customers runs an OAS 10g (9.0.4.0.0) that originally ships with the very old classes12dms.jar as the Oracle JDBC Driver. Now for various reasons we cannot use this driver for our newly developed application but expect an up2date JDBC driver to be used instead.
I've found a couple of references in the forums pointing to this metalink article:
"JDBC Driver Upgrade Notes in OC4J/OracleAS"
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=275645.1
However, we cannot use the process described in there because it describes how to update the driver globally but we are not able to globally update the driver in order to ensure that existing applications on the server are not influenced by our driver update.
So is there a way to make this application specific? I do have some weblogic experience and I know that it is doable there, so I guess there should be a way in OAS as well ... hopefully :-)
tia
Udo Rader

Thanks. I got this patch # from MetaLink and applied the same. Now I get the following error:
Error encountered initializing
users and groups using the specified user manager. com.evermind.sql.DataSourceUserManager does not support the operations needed to populate
this page.. getGroupCount() is not supported by this UserManager
Trace
=====================
2004-03-26 16:39:57,481 [HttpRequestHandler-18670253] ERROR ias.ErrorData errHandler.62 - error during page render Error encountered initializing
users and groups using the specified user manager. com.evermind.sql.DataSourceUserManager does not support the operations needed to populate
this page.. getGroupCount() is not supported by this UserManager
oracle.sysman.emSDK.admObj.AdminObjectException: Unsupported operation exception encountered
at oracle.sysman.ias.sta.oc4j.UserMgrAdmin.initGroups(UserMgrAdmin.java:742)
at oracle.sysman.ias.sta.oc4j.UserMgrAdmin.getGroupsFromUserMgr(UserMgrAdmin.java:138)
at oracle.sysman.ias.sta.oc4j.AppSecurity.getGroupsData(AppSecurity.java:664)
Caused by: java.lang.UnsupportedOperationException: getGroupCount() is not supported by this UserManager
at com.evermind.security.AbstractUserManager.getGroupCount(AbstractUserManager.java:222)
at oracle.sysman.ias.sta.oc4j.UserMgrAdmin.initGroups(UserMgrAdmin.java:730)
... 207 more
java.lang.UnsupportedOperationException: getGroupCount() is not supported by this UserManager
at com.evermind.security.AbstractUserManager.getGroupCount(AbstractUserManager.java:222)
at oracle.sysman.ias.sta.oc4j.UserMgrAdmin.initGroups(UserMgrAdmin.java:730)
at oracle.sysman.ias.sta.oc4j.UserMgrAdmin.getGroupsFromUserMgr(UserMgrAdmin.java:138)
at oracle.sysman.ias.sta.oc4j.AppSecurity.getGroupsData(AppSecurity.java:664)
====================================
Where do I go from here?

Upgrade Oracle iAS 9.0.4.1 JDBC Driver to 9.2.0.8

Hi,
I'm using Oracle Application Server 10g R1 (9.0.4.1) for a JDBC application that connects to an Oracle 9.2.0.7 Database.
Due to some NLS problems with JDBC connections which are out of the scope of this posting, I need to upgrade the JDBC Driver of iAS 9.0.4.1 to the latest JDBC Driver, closest to my database full version. Since there is no 9.2.0.7 JDBC Driver set, I downloaded the 9.2.0.8 JDBC Driver files for Java JRE 1.4 which is the jdk/jre of the iAS 9.0.4.1.
This set though, contains files ojdbc14.jar, ojdbc14_g.jar and ocrs12.jar and NOT the JDBC Driver files that are found in the ORACLE_HOME\jdbc\lib path of the iAS 9.0.4.1., and of course, replacing the existing with the new ones, does not work (does not update the JDBC Driver on the server).
How can this upgrade be archived?
Is anyone aware of the documented JDBC upgrade procedure for Oracle iAS 9.0.4.1, to driver version 9.2.0.8?
Why there is no classes12.zip or classes12.jar distribution in the JDBC driver 9.2.0.8 set?
Thank you

JspServlet: unable to dispatch to requested page: Exception:java.lang.UnsupportedClassVersionError: wfrecruit/WFRequisition (Unsupported major.minor version 49.0)
Application is compiled with a JDK version and run with another version of JDK.
Compile and run application with same version of JDK.

JDBC Driver 10.1.0.5 to 10.2.0.3 Upgrade Exception: Socket is not connected

Environment -
Oracle TopLink 10g Release 3 (10.1.3.3.0) (Build 070620)
Oracle 10g Release 3 (10.1.3) Application Server
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
JDBC Driver: 10.2.0.3
Problem -
I am trying a simple upgrade of my JDBC driver from 10.1.0.5 to 10.2.0.3. I have tried via creation of a shared library according to the OC4J Configuration and Administration Gude, and I even tried a direct replacement of jar files located under <OC4J_HOME>/jdbc/lib. After many deploy/undeploys and server restarts I continually receive the same error when TopLink attemps a datasource login:
oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Io exception: Socket is not connectedError Code: 17002
at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:276)
at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:115)
at oracle.toplink.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:147)
at oracle.toplink.intersnal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:228)
Has anyone seen or experienced this before? Thanks!

Hi Srini,
There are other errors:
83: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/u01/oracle/oradata/patriadb/ptlidx.dbf'
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
Failing sql is:
CREATE TABLESPACE "PORTAL_IDX" DATAFILE '/u01/oracle/oradata/patriadb/ptlidx.dbf' SIZE 20971520 AUTOEXTEND ON NEXT 31457280 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MA
ORA-39083: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/u01/oracle/oradata/patriadb/ptllog.dbf'
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
Failing sql is:
CREATE TABLESPACE "PORTAL_LOG" DATAFILE '/u01/oracle/oradata/patriadb/ptllog.dbf' SIZE 4194304 AUTOEXTEND ON NEXT 31457280 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MAN
ORA-39083: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/u01/oracle/oradata/patriadb/oca.dbf'
47,1
I guess the point is, should I use IMPDP using Network link?
the doc seems to suggest this will work better

Upgrade MS SQL 2005 platform to MS SQL 2008 - Update the JDBC driver...

Hello to all,
This is the second post that I created reporting this error because in the first one I open this message in group of "SAP on SQL Server" but without any kind of help from community:
My problem is...
I´m planning to do an upgrade of a sap system (SAP ECC 6.0) from SQL Server 2005 to a SQL Server 2008 but I´m facing with a little problem. This system has two stacks - ABAP + JAVA - and because of that the Upgrade Guide to MS SQL Server 2008 describe which are the requirements for this upgrade DB platform, and one of them is this:
"If you use a Java system, you have updated the JDBC driver as described in SAP Note 639702"
... the updated of JDBC driver when we have in system a Java part, like it has in this case! But I´m with a serious problems to find in SAP System Files in Windows 2003 Server the four files that is mentioned in that note 639702. I can´t find it anywhere... in note says:
Depending on the SAP release and the system configuration, the driver files base.jar, util.jar, sqlserver.jar, and spy.jar are available in an installed system at:
(NetWeaver'04, Java:) usrsap<SAP SID>JC<InstanceNumber>j2eejdbc
(NetWeaver'04, ABAP+Java:) usrsap<SAP SID>DVEBMGS<InstanceNumber>j2eejdbc
(NetWeaver 2004s:) usrsap<SAPSID>SYSexe<NUC|UC>Platformmssjdbc
But... still I didn´t find them! I also read other note 1109274 - New JDBC driver for NetWeaver 7.0 and higher but even so I still can´t find it!
Can you help me to find this files on my operation system? I have to update that JDBC... but of course for this task I have to find it first!!!
Best regards,
João Dimas - Portugal

Hi,
Have you considered the possibility that the directory that was supposed to contain the jdbc drivers has been replaced by a recent kernel upgrade and you never noticed?
Anyway, looking forward, put in a new set of JDBC drivers in the correct location.
Also, with reference to the following point from the first note:
Check your JDBC Driver version before you download it. To do this, unpack the attached check tool SAPCheckVersion in the relevant JDBC directory (refer to the previous paragraph). Then open a command prompt there and execute the following command:
SAPCheckVersion.cmd <server name> <username> <password>
Replace <server name> with the name of the database server, <username> and <password> with the logon data of an SQL user (for example, sa or SAP<SID>DB). If you call SAPCheckVersion.cmd without a parameter, the system displays detailed help. The tool supports both DataDirect and Microsoft drivers.
*The download name tells you which version of the driver you need to download from SAP Service Marketplace.*
Run this SAPCheckVersion and find out which drivers you need to download and then download them and use them.
Regards,
Shitij

Upgrade MS SQL 2005 platform to MS SQL 2008 - Update the JDBC driver issue

Hello to all,
I´m planning to do an upgrade of a sap system (SAP ECC 6.0) from SQL Server 2005 to an SQL Server 2008 but I´m facing with a little problem. This system has two stacks - ABAP + JAVA - and because of that the Upgrade Guide to MS SQL Server 2008 describe which are the requirements for this upgrade DB platform, and one of them is this:
"If you use a Java system, you have updated the JDBC driver as described in SAP Note 639702"
... the updated of JDBC driver when we have in system a Java part, like it has in this case! But I´m with a serious problems to find in SAP System Files in Windows 2003 Server the four files that is mentioned in that note 639702. I can´t find it anywhere... in note says:
Depending on the SAP release and the system configuration, the driver files base.jar, util.jar, sqlserver.jar, and spy.jar are available in an installed system at:
(NetWeaver'04, Java:) usrsap<SAP SID>JC<InstanceNumber>j2eejdbc
(NetWeaver'04, ABAP+Java:) usrsap<SAP SID>DVEBMGS<InstanceNumber>j2eejdbc
(NetWeaver 2004s:) usrsap<SAPSID>SYSexe<NUC|UC>Platformmssjdbc
But... still I didn´t find them! I also read other note 1109274 - New JDBC driver for NetWeaver 7.0 and higher but even so I still can´t find it!
Can you help me to find this files on my operation system? I have to update that JDBC... but of course for this task I have to find it first!!!
Best regards,
João Dimas - Portugal

Hello John Feely,
Yeah I already know that you mentioned! In my first post/previous message I mentioned that, I already read the note 639702 and it was there I read that explanation... regarding that creation that you refer in the case of files are not in those directories, so you said that I could download this four files and put in there... but where? and how..? Sorry but that solution seems does not make any sense!
I also look other systems with double stack ABAP + JAVA and I one more time I didn´t see that directories or files that are mentioned in that note!! DAMN!
Any tip?
Kind regards,
João Dimas - Portugal

Upgrade jdbc driver in jdeveloper

Hi,
We have build an application in jdev 10.1.3.3.0 which connects to a database 10.2.0.3.0.
We have been experiencing performance issues during the execution of some of our queries.
When executing this query outside jdeveloper (sqldeveloper, sqlnavigator), performance is ok, and explain plan is as expected.
When exactly the same query is executed from within Jdeveloper, (application and SQL worksheet) the explain plan gets messed up and performance is bad.
We suspect this has to do with the version of the JDBC Client.
As in the past we experienced similar behaviour when running queries from older Oracle clients (fi. 10g rel 1).
Can someone indicate on how we can check and upgrade the version of the JDBC driver Jdeveloper is using.
thanks,
Gert

You can upgrade your JDBC driver by doing the next steps:
1. Download JDBC driver from
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
2. Browse to <JDeveloper_home>\jdbc\lib
3. Replace the existing files with the new files you have downloaded (you might need to make a backup first)
4. Now, you have successfully upgraded your JDBC driver.

Upgrade of JDBC driver

Dear all,
As of now i am using jdbc driver and it is working very fine for ms-sql-2005.
Now new system has come into landscape ms-sql-2008 64bit os.
now my comunication channel showing error need to upgrade my jdbc driver.
So please help me how i need to upgrade. If i do any upgrade there will be any effect for the present comunication channel which are working.. to ovide this what we need to take care.. i have gon through this document. but is this same we need to do for sap-pi-7.0
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f
Regards
Vijay

Hi,
As per document i have done the deployment now all the channels which are working for ms-sql2005 are throughing errors..the error is
Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://xxxxxxxx:1433;databaseName=yyyyy': UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 49.0)
So now what we can do again redeploy the old file or any other option.
there might me new driver class and url format for sqlserver 2008.. if nay one knows that please share that. as rite now i am using..
Driver class: com.microsoft.sqlserver.jdbc. SQLServerDriver
URL :jdbc:sqlserver://<db_Server>:port;databaseName=< db_name>
Regards
Vijay
Edited by: vijay Kumar on Feb 24, 2009 8:34 PM
Edited by: vijay Kumar on Feb 24, 2009 8:36 PM

Oracle Application Server 4.0.8.2 upgrade JDBC driver how ?

What I did was I replace the following classes12.zip (thid JDBC driver is from Jdeveloper library folder) file into OAS home directory under jdbc/lib and change the following env variables in OAS.
Lastly, tested out 2 simple servlet program
1) No Connection pooling (simple query)
2) With Connection Pooling (only JDBC 2 has this features)
both the servlet fail to display and throw me an error "An Application has occured error ..."
with the old classes111.zip it works fine not after I replaced the new JDBC 2 driver.

sorry Oracle Application Server 4.0.8.1

Problem with Java 5 and Oracle 10g JDBC driver

Hi All,
Currently we upgrade our web application to Java 5 and Oracle 10.2 JDBC driver. And we encountered a bug, when the user entered the information through UI and data didn't store into database (Oracle 9i). The problem is that this bug is not happend so often maybe once a day and this did not happen before we upgraded to Java 5 and Oracle 10.2 JDBC driver. Does anyone encounter the same problem ? Is this Java 5 problem or Oracle JDBC driver problem ?
Thanks,

sounds like a database problem...
Are you using a driver version that's supported for your database engine?
What else did you change? We once ran into a major bug in our application that had for 5 years been masked by performance problems in our hardware and infrastructure.
Once those were resolved the bug showed itself and caused tens of thousands of records to be erroneously inserted into our database every day.
It's certainly NOT a problem with your JVM (if it's a decent one, like the Sun implementation).
So it's either your database, your driver, your network (dropping packets???), or your application.
The upgrade may just have exposed something that was already there.

Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

I'm using oci8 to connect to the Oracle database.
URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
When I tried to start the weblogic server, I got the following errors:
Can you suggest what I should do next (step-wise)??? Thanks, Bobby
<Sleeping in createResource()>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001060> <Cannot startup connection pool
"pool/test_myapp" weblogic.common.ResourceException:
Could not load 'oracle.jdbc.driver.OracleDriver
If this is a type-4 JDBC driver, it could occur if the JDBC
driver is not in the system CLASSPATH.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system
or in your PATH environment variable.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://e-docs.bea.com
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java: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(DeploymentTarget.java:360)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.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:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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 $Proxy31.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.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:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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 $Proxy42.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)
>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001082> <Creating Data Source named
jdbc/test_myapp for pool pool/test_myapp>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001070> <Checking existence of connection pool
pool/test_myapp requested by user system>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
be created with non-existent Pool (connection or multi)
(pool/test_myapp)>
####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
<main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160001> <Error deploying application myapp-ejb:
Unable to deploy EJB: Counter from myapp-ejb.jar:
The DataSource with the JNDI name: jdbc/test_myapp could not be
located. Please ensure that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor
is correct.
>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101031>
<[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101032>
<[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
successfully...>
####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
<myserver> <main> <system> <> <100037> <Creating SessionContext of
type: memory for webapp: /myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering getior
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
servlets with initArgs 'wl-dispatch-policy=direct'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101097> <Registering ServletContext:
"myapp:/myapp">
####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160003> <Deployed : myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101133> <Initializing WEB server myserver>
####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141052> <Application Poller started for
development server.>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <ListenThread> <system> <> <000202> <ListenThread listening
on port 7001>
####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
was built on Nov 1 2001 16:39:28
>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
listening on port 7002>
####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141030> <Starting discovery of Managed
Server... This feature is on by default, you may turn this off by
passing -Dweblogic.management.discover=false>
####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
"myserver" for domain "mydomain" running in Development Mode>
####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Allocating: '2' NT reader threads>
####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: Using standard I/O>

"thorick" <[email protected]> wrote in message news:<[email protected]>...
Most likely, the OCI libraries could not be loaded.
Before continuing down this path, is there any reason
why you want to use an OCI based Driver as opposed to the
all Java Oracle thin driver ?There is indeed a valid reason for my choice.
I am currently connecting to the Oracle "Rdb" 7.0 database (located on
VMS) - not Oracle Oracle.
The SQL Service software we're currently using is version 7.1. This
version works well with the OCI8 driver (when connecting to the
database from Windows NT). This version of SQL Service however does
NOT work for the THIN driver (unless we upgrade the SQL Service to
version 7.1.5.5 - which we're not prepared to do so because it is not
stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
works for THIN driver but it will result in uncommitted
transactions/unresolved connection/stopping of listener issues and
there is a need to restart the service from time to time. Oracle has
since confirmed that this is a bug that they have yet to resolve...
So we have to stick to OCI8 (THICK) for the time being. I would really
appreciate it very much if you can tell me the various OCI libraries
that I need to load (in terms of WebLogic Server config file settings
etc..).
By the way I have already installed the Oracle 8 client software on
the NT server (where WebLogic Server is) and I have also set up the
relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
database on the VMS. I have also tried using SQL*Plus to connect to
the database and I can connect properly to the database. But WebLogic
simply doesn't seem to load the software.
Help...
Regards,
Bobby Brown, writing from Australia.

Multibyte character support in Jdbc Driver

Hi,
I want to use multibyte characters in my Application and to store it in my database.
If my database provider does not support a Multibyte data type, Can my
Jdbc Driver provide support for the same ?
For a column of type ISO88591 which is of single byte by nature , Can we insert Multibyte characters by providing some support for the same in my Jdbc Driver ?
If yes , How could this support be provided in the Jdbc Driver.
Please provide some clarification on the same.
Thanks in Advance,
Jay

Hi,
I want to use multibyte characters in my Application
and to store it in my database.
If my database provider does not support a Multibyte
data type, Can my
Jdbc Driver provide support for the same ?
For a column of type ISO88591 which is of single byte
by nature , Can we insert Multibyte characters by
providing some support for the same in my Jdbc Driver
This is a very very bad idea in general. If your database is Oracle, it's a horrificly stupendously bad idea.
First, collation ("ORDER BY" and other things) will be badly broken.
Second, it will very likely prevent the database from being upgraded to a multi-byte version.
Third, it commonly will cause various database utilities to not work.
There are plenty of databases, many of them free, that support UTF8.

Oracle JDBC driver 11.2.0.3 is reported as client version 11.2.0.2

Greetings everyone,
I wonder if other folks are experiencing the same:
We have upgraded our JDBC driver to latest ojdbc6.jar (2,714,189 bytes) - 11.2.0.3
Everything looks great, except that on the server side it is reported as client version 11.2.0.2
JVM side:
===== Database info =====
DatabaseProductName: Oracle
DatabaseProductVersion: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
DatabaseMajorVersion: 11
DatabaseMinorVersion: 2
===== Driver info =====
DriverName: Oracle JDBC driver
DriverVersion: 11.2.0.3.0
DriverMajorVersion: 11
DriverMinorVersion: 2
Database side:
select client_driver, client_version from v$session_connect_info
(null), 11.2.0.2.0
Is that expected behavior or the property is not updated between releases?
Andrey
Edited by: 907164 on Jan 10, 2012 12:09 PM

Hi ,
Thank you so much for your reply.
That was the exact information that I needed.
Could you also tell me from where can I get the information of future releases.
Regards,
Stacey.

How to find out the cause of "Cannot create JDBC driver"?

A small Java web application constantly runs into a problem of "Cannot of create JDBC driver of class 'org.postgresql.Driver' for connect URL 'jdbc:postgresl://localhost:5432/myapp'". The problem still exists after upgrading the driver. After recycling the server, this problem will be resolved. It, however, will come back after a while.
Any suggestions to solve this problem?
Thanks a lot.

jschell wrote:
vwuvancouver wrote:
Any suggestions to solve this problem?To start with get the full and complete stack trace.
However since it is an intermittent problem there are only two possibilities
1. You have some code that is written correctly and some that is not.
2. It is a resource not code usage problem. Such as that you are not closing all result sets, statements and connections.Here is related log messages:
2009-04-30 09:29:21,386 INFO XmlWebApplicationContext:601: - Closing application context [WebApplicationContext for namespace 'mybookmarks-servlet']
2009-04-30 09:29:21,387 INFO DefaultListableBeanFactory:273: - Destroying singletons in {org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [messageSource,viewResolver,localeResolver,untapedUrlMapping,urlMapping,localeChangeInterceptor,errorsController,myBookmarksController,bookmarkController,reminderController,accountController,userControllerMethodResolver,userFormController,searchFormController,directoryController,directoryControllerMethodResolver,secureHandlerMapping,signonInterceptor,addBookmarkFromListFormController,addBookmarkFormController,bookmarkValidator,editWebSiteEntryFormController,addCommentFormController,reminderFormController,genericReminderFormController,alterReminderDateFormController,contactFormController,invitationFormController,propertyConfigurer,mailSender]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [propertyConfigurer,mailSender,userValidator,bookmarkService,dataSource,sessionFactory,transactionManager,accountDao,categoryDao,webSiteDao,siteVisitDao,reminderDao,commentDao,bookmarkDao]; root of BeanFactory hierarchy}
2009-04-30 09:29:21,388 INFO GenericWebApplicationContext:601: - Closing application context [org.springframework.web.context.support.GenericWebApplicationContext;hashCode=15954072]
2009-04-30 09:29:21,389 INFO DefaultListableBeanFactory:273: - Destroying singletons in {org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [modelView,addCommentFormView,discoveryFormView,mostVisitedView,bookmarkListView,contactFormView,actionResultView,accountView,reminderFormView,reminderDateFormView,searchList2View,helpView,homeView,taggedListView,searchFormView,reminderListView,webSiteEntryFormView,reminderForm2View,categorizedList2View,invitationFormView,myHomeView,taggedList2View,contactListView,aboutView,bookmarkFormView,bookmarkForm2View,newEntries2View,categorizedListView,signinFormView,accountActionResultView,userFormView,siteActionResultView,searchListView,mostVisited2View,newEntriesView,errorHttp404View]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [messageSource,viewResolver,localeResolver,untapedUrlMapping,urlMapping,localeChangeInterceptor,errorsController,myBookmarksController,bookmarkController,reminderController,accountController,userControllerMethodResolver,userFormController,searchFormController,directoryController,directoryControllerMethodResolver,secureHandlerMapping,signonInterceptor,addBookmarkFromListFormController,addBookmarkFormController,bookmarkValidator,editWebSiteEntryFormController,addCommentFormController,reminderFormController,genericReminderFormController,alterReminderDateFormController,contactFormController,invitationFormController,propertyConfigurer,mailSender]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [propertyConfigurer,mailSender,userValidator,bookmarkService,dataSource,sessionFactory,transactionManager,accountDao,categoryDao,webSiteDao,siteVisitDao,reminderDao,commentDao,bookmarkDao]; root of BeanFactory hierarchy}
2009-04-30 09:29:21,391 INFO GenericWebApplicationContext:601: - Closing application context [org.springframework.web.context.support.GenericWebApplicationContext;hashCode=29369879]
2009-04-30 09:29:21,392 INFO DefaultListableBeanFactory:273: - Destroying singletons in {org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [modelView,addCommentFormView,discoveryFormView,mostVisitedView,bookmarkListView,contactFormView,accountView,actionResultView,reminderFormView,reminderDateFormView,searchList2View,helpView,homeView,configView,taggedListView,searchFormView,reminderListView,webSiteEntryFormView,reminderForm2View,categorizedList2View,invitationFormView,taggedList2View,myHomeView,contactListView,aboutView,bookmarkFormView,bookmarkForm2View,newEntries2View,categorizedListView,signinFormView,accountActionResultView,userFormView,siteActionResultView,searchListView,mostVisited2View,newEntriesView,errorHttp404View]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [messageSource,viewResolver,localeResolver,untapedUrlMapping,urlMapping,localeChangeInterceptor,errorsController,myBookmarksController,bookmarkController,reminderController,accountController,userControllerMethodResolver,userFormController,searchFormController,directoryController,directoryControllerMethodResolver,secureHandlerMapping,signonInterceptor,addBookmarkFromListFormController,addBookmarkFormController,bookmarkValidator,editWebSiteEntryFormController,addCommentFormController,reminderFormController,genericReminderFormController,alterReminderDateFormController,contactFormController,invitationFormController,propertyConfigurer,mailSender]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [propertyConfigurer,mailSender,userValidator,bookmarkService,dataSource,sessionFactory,transactionManager,accountDao,categoryDao,webSiteDao,siteVisitDao,reminderDao,commentDao,bookmarkDao]; root of BeanFactory hierarchy}
2009-04-30 09:29:21,394 INFO XmlWebApplicationContext:601: - Closing application context [Root WebApplicationContext]
2009-04-30 09:29:21,395 INFO DefaultListableBeanFactory:273: - Destroying singletons in {org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [propertyConfigurer,mailSender,userValidator,bookmarkService,dataSource,sessionFactory,transactionManager,accountDao,categoryDao,webSiteDao,siteVisitDao,reminderDao,commentDao,bookmarkDao]; root of BeanFactory hierarchy}
2009-04-30 09:29:21,396 INFO LocalSessionFactoryBean:184: - Closing Hibernate SessionFactory
2009-04-30 09:29:21,397 INFO SessionFactoryImpl:767: - closing
2009-04-30 09:29:21,408 WARN JDBCExceptionReporter:71: - SQL Error: 0, SQLState: null
2009-04-30 09:29:21,410 ERROR JDBCExceptionReporter:72: - Cannot create JDBC driver of class 'org.postgresql.Driver' for connect URL 'jdbc:postgresql://localhost:5432/homepage'
2009-04-30 09:29:21,411 WARN JDBCExceptionReporter:71: - SQL Error: 0, SQLState: null
2009-04-30 09:29:21,414 ERROR JDBCExceptionReporter:72: - Cannot create JDBC driver of class 'org.postgresql.Driver' for connect URL 'jdbc:postgresql://localhost:5432/homepage'
...Your analysis seems very reasonable. As the above log messages, this application is built on Hibernate and Spring. All back end is taken care by Hibernate. I don't have a direct control on it. I should ask the Hibernate crowd about this issue. The Hibernate forum is still down at this moment.
Edited by: vwuvancouver on Apr 30, 2009 1:12 PM

Can't connect using OCI JDBC driver in OC4J 10.1.3.3 standalone

Hi all,
I've recently upgraded my JDev from 10.1.3.2 to 10.1.3.3 and now I'm unable to establish any OCI connections with my local Oracle 10.1.0.4 database. Not even through a connection pool. The strangest thing is that when I test an OCI connection running from JDeveloper it works fine and the JDBC jars and the oci client are exactly the same.
The error is always the same when I execute a test on a connection pool using the OCI driver:
WARNING J2EE DS-00001 Exception occurred testing connection. Exception: java.sql.SQLException: Closed Connection.
If I just change the driver to the THIN one, the same test works. If I take the same URL from the OCI test and use it in a test class and run it inside JDeveloper, it works also.
I've even downloaded the instant client 10.1.0.5 (which happens to be exactly the same version of the JDBC driver that comes with JDev 10.1.3.3) and tried to use it with no success.
THIN connections are working just fine. The problem happens only when I try to connect via OCI and this problem was not happening in version 10.1.3.2.
Any help?

I found the cause of this problem. It turns out that you must be very careful with the environment variable ORACLE_HOME. On Windows, normally, we don't even set this variable because most applications are able to get it from the system's registry.
Well, it happened that I've edited the script start_oc4j.bat and, for organization reasons, I set the ORACLE_HOME variable with my JDeveloper's home directory (which is the same as my OC4J standalone's). By doing that, I kind of confused the OCI client. Once I removed the "set ORACLE_HOME=C:\JDev" line from the script, everything worked just fine again.
So, always remember: avoid setting environment variable ORACLE_HOME when using Windows and, if you must set it, be sure to do it right.
Regards,
Eduardo.

JDBC Driver Upgrade

Similar Messages

Maybe you are looking for