WSAD 5.1.2Upgrading JDBC Driver to 10g

Hi,
I'm having a bloody annoying problem in my WSAD 5.1.2, I am trying to upgrade the jdbc driver to the latest one (10g) but the damn thing does not work !
I replaced the classes12.jar with the ojdbc14.jar and changed the datasource accordingly, now I get a NullPointerException in the WSAD when it starts.
Anybody?
[13:24:50:587 GMT+02:00 22/08/05] 30f81d3b ConnectionPoo W CONM6024W: An Exception, (java.lang.NullPointerException
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:79)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:59)
     at com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectionFactory.java:32)
     at com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:1310)
     at com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.java:1208)
     at com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:1134)
     at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:972)
     at com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:905)
     at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:390)
     at com.ibm.ejs.cm.DataSourceImpl$1.run(DataSourceImpl.java:154)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java:351)
     at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:152)
     at com.ibm.ejs.persistence.EJSJDBCPersister.initialize(EJSJDBCPersister.java:442)
     at com.ibm.ejs.persistence.EJSJDBCPersister.create(EJSJDBCPersister.java:196)
     at com.ibm.ws.cpi.JDBCPersisterFactoryImpl.create(JDBCPersisterFactoryImpl.java:102)
     at com.ibm.ejs.container.BeanMetaData.completeInitialization(BeanMetaData.java:1291)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createBeanMetaData(EJBContainerImpl.java:1039)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createModuleMetaData(EJBContainerImpl.java:830)
     at com.ibm.ws.runtime.component.EJBContainerImpl.createMetaData(EJBContainerImpl.java:1575)
     at com.ibm.ws.runtime.component.MetaDataMgrImpl.createFactoryMetaData(MetaDataMgrImpl.java:115)
     at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:159)
     at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:350)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:311)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:268)
     at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
     at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
     at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
     at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
     at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
     at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
     at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
     at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:204)
     at java.lang.Thread.run(Thread.java:567)
), was caught in createConnection method.

It's hard to tell, but my thought is that maybe the driver is not consistent with the database version of DB2 that you are using.
Be sure that the driver is the correct version for the database to which you are attempting to connect.

Similar Messages

Oracle JDBC driver 10g and xMII

I have a BLS that tries inserting CLOB data into Oracle 10g database. Since Oracle 8 JDBC driver does not support that (I saw other SDN messages on the same issue), I have download and copied Oracle JDBC driver for 10g
ojdbc14.jar to
C:\ServletExec AS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib
folder
I restarted Servlet exec engine and I'm still seeing the same error
that the value to be inserted is too large ( I'm inserting more than
4000 characters but much lesser than 4 GB which CLOB column can take)
1. I want to understand if there is something else that I need to
change in order for xMII to pickup the new driver.
2. Also, should I add it classpath?
3. Looking at some Oracle notes on using capability of 10g driver for
manipulating large data, the property SetBigStringTryClob=true should
be set. I saw examples of some non-xMII applications setting it in their
servers.xml. Similarly, in which file can I set this property in xMII
to force the driver to use this feature?
Is ServerDefaults.xml under C:\Lighthammer\Illuminator\SysConf the
right place? Since it is not recommended to modify the configuration
files manually rather than using admin console, I'm not sure on this
one.
Let me know
Thanks

Are you really sure this "SetBig.." thing is the solution?
Searching for the ORA error you posted results in quite a few solutions in the way you write your SQL statement.
Maybe changing your statement might help.
If you don't mind can you post the SQL statement?
Another good test would be to see if the SQL statement goes through without any errors when used from a different SQL editor.I would suggest do that first if you haven't already.

Problem with JDBC driver for Oracle 10g

Hi.
I've successfully accessed a MySQL database via a DataSource from a servlet (that uses a DAO). However, when I try to do the same with an Oracle 10g Database, I get the error message:
Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver'
I'm using J2SE1.5.0/5.0 and ojdbc14.jar, the latter of which I downloaded this afternoon as the latest driver JAR available on the Oracle site. As with the MySQL driver, I've placed it in the commons\lib folder within Tomcat. (I've also, of course, made the necessary modifications to server.xml and web.xml.)
Upon examining the ReadMe file at the top of the Oracle download page, I found that the oracle.jdbc.driver package is now deprecated and all references to oracle.jdbc.driver should be replaced with oracle.jdbc. However, I got a similar error message when I tried this modification. Upon examining the contents of ojdbc.jar, I found that the driver was there and that it was, in fact, still oracle\jdbc\driver\OracleDriver!
It appears as though the Oracle site has not been updated with a driver that matches its latest documentation. However, this does not explain why the driver is not even being loacted when it is in the correct place. Can anybody shed any light on this? Any help would be much appreciated.
Thanks in anticipation.
Cheers.
Jan

I've successfully accessed a MySQL database via a
DataSource from a servlet (that uses a DAO). However,
when I try to do the same with an Oracle 10g
Database, I get the error message:
Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver'
That's different from a ClassNotFoundException.
>
I'm using J2SE1.5.0/5.0 and ojdbc14.jar, the latter
of which I downloaded this afternoon as the latest
driver JAR available on the Oracle site. So you got ojdbc14.jar or ojdbc14_g.jar under the 10g drivers?
As with the
MySQL driver, I've placed it in the commons\lib
folder within Tomcat. I think it's a better idea to put in the WEB-INF/lib directory of your Web app rather than commons/lib. WAR files are a very good idea, too.
(I've also, of course, made the
necessary modifications to server.xml and web.xml.)So you're using a JNDI data source? It sounds to me like that's where the problem is.
You should not have to edit the server.xml at all. If you put the <ResourceParams> in a context XML file with the same name as your WAR file into the TOMCAT_HOME/webapps directory it'll be picked up automatically. (It might also be accessible in the META-INF directory for your app, but I haven't done it that way.)
Upon examining the ReadMe file at the top of the
Oracle download page, I found that the
oracle.jdbc.driver package is now deprecated and all
references to oracle.jdbc.driver should be replaced
with oracle.jdbc.
However, I got a similar error
message when I tried this modification. Upon
examining the contents of ojdbc.jar, I found that the
driver was there and that it was, in fact, still
oracle\jdbc\driver\OracleDriver! The fully-resolved class name you should be using MUST match the class that's in the ojdbc14.jar that you're using. Look in the JAR for the definitive answer: the one that I downloaded is still using the oracle.jdbc.driver package for OracleDriver.class. Ignore the docs - use the name that's in the JAR.
It appears as though the Oracle site has not been
updated with a driver that matches its latest
documentation. That often happens with docs.
However, this does not explain why the
driver is not even being loacted when it is in the
correct place. Can anybody shed any light on this?
Any help would be much appreciated.I think the problem lies in your web.xml and server.xml
I'd recommend that you decouple the JDBC from the Web app for now. See if you can connect to Oracle using a simple desktop app and leave the Web piece out of the equation for now. Once you can do that, you'll be certain that the parameters you're using are correct and you can turn your attention to getting the Tomcat configuration right.
PS - I'm using Oracle 9.2.0.1 and Tomcat successfully right now, so it can be done.

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?

SetString/executeBatch fails in Oracle 10g OCI JDBC driver

Hi,
I am using Oracle 10g OCI jdbc driver for batch updates.
Following is the the code that I am using
import java.sql.*;
import oracle.jdbc.*;
import oracle.jdbc.pool.OracleDataSource;
public class BatchUpdates
public static void main(String[] args)
Connection conn = null;
Statement stmt = null;
PreparedStatement pstmt = null;
ResultSet rset = null;
int i = 0;
try
String url = "jdbc:oracle:oci:@kctutf8";
try {
String url1 = System.getProperty("JDBC_URL");
if (url1 != null)
url = url1;
} catch (Exception e) {
OracleDataSource ods = new OracleDataSource();
ods.setUser("kctuser");
ods.setPassword("kana");
ods.setURL(url);
conn = ods.getConnection ();
stmt = conn.createStatement();
try { stmt.execute(
"create table mytest_table (col1 number, col2 varchar2(20))");
} catch (Exception e1) {}
pstmt = conn.prepareStatement("insert into mytest_table values (?, ?)");
pstmt.setInt(1, 1);
pstmt.setString(2, "row 1");
pstmt.addBatch();
pstmt.setInt(1, 2);
pstmt.setString(2, "row 2");
pstmt.addBatch();
pstmt.setInt(1, 3);
pstmt.setString(2, "row 3");
pstmt.addBatch();
pstmt.setInt(1, 4);
pstmt.setString(2, "row 4");
pstmt.addBatch();
pstmt.setInt(1, 5);
pstmt.setString(2, "row 5");
pstmt.addBatch();
pstmt.executeBatch();
rset = stmt.executeQuery("select * from mytest_table");
while (rset.next())
System.out.println(rset.getInt(1) + ", " + rset.getString(2));
catch (Exception e)
e.printStackTrace();
finally
if (stmt != null)
try { stmt.execute("drop table mytest_table"); } catch (Exception e) {}
try { stmt.close(); } catch (Exception e) {}
if (pstmt != null)
try { pstmt.close(); } catch (Exception e) {}
if (conn != null)
try { conn.close(); } catch (Exception e) {}
When I run this class I get the following output
1, row 1
2, row 3
3, row 5
4, null
5,
But It should have been
1, row 1
2, row 2
3, row 3
4, row 4
5, row 5
The same class runs fine if I use Thin driver.
Can anyone please help me solve this issue.
Note: This happens only in case we use setString with Varchar2 in the DB. This works fine if I have two number columns
Thanks,
Raja.S

Please post this question to the Java forum. It is located under "Technologies".

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.

Which ojdbc14.jar JDBC driver to use for Oracle 10g database

When ODI is installed there seems to be an Oralce JDBC driver in place in the drivers folder (ojdbc14.jar).
When we connect to an Oracle datastore and point to a table and use the 'reverse' function to populate the columns - it sort of works OK but does not bring back the datatypes properly. This is found to be when the Oracle table has UNICODE character datatypes NCHAR and NVARCHAR. If a table has CHAR and VARCHAR it is all OK but any table that has UNICODE datatyoe has a problem.
Is this likely to be the JDBC driver ?
We have tried replacing this ojdbc14.jar with the older classes12 and this, as expected, did not resolve the issue.
We then tried replacing it with the latest 10.2.0.4 ojdbc14.jar but again no difference.
Does anyone have any experience with Oracle JDBC drivers and what release level to use - and using against UNICODE datatypes in tables ?
Regards

Our problem is that when we use 'reverse' to populate the columns from a physicla table in an Oracle database - ODI is obviously 'seeing' the ORacle table and is correctly understanding the columns in the table and defining them in it's model - but wherever there is a column with a datatype in the ORacle database of NCHAR or NVARCHAR it fails to populate the datatype or the 'length' of these columns. If I manually try to specify the datatype these 2 unicode data types do NOT exist in the pull down list of datatypes.
I see what you are asking - if these datatypes are actually defined as datatypes within the actual technology - I cant access my lab right now but will check as soon as I can. Thanks for the suggestion.

Which Oracle JDBC Driver to use with WSAD 5.1.2?

Hi,
I will appreciate if someone could help me with:
1) Whether I should select "Oracle JDBC Driver" or "Oracle JDBC Driver (XA)" as the JDBC Provider Type. The rest in the list (Thin & oci8 ) are deprecated.
2) When I go to create a datasource, for either of the above JDBC provider type, I get the options:
- User defined JDBC provider
- Oracle JDBC provider
- Oracle JDBC Thin Driver
- Oracle JDBC oci8 Driver
Why do I have the Thin and Oci8 option here, when those were shown as deprecated under JDBC Provider Type?
Please help to clear up this confusion.
-Nimmi

This is what I did for my DS settings
1. select Oracle JDBC Driver
2. set Classes12.jar in Websphre classpath - (Oracle thin driver)
3. create DS with option User defined JDBC provider
means I have added Thin driver provided by Oracle , instead of deprecated Thin driver from IBM.

To change the JDBC driver for a single OC4J instance

Hello,
I implemeted an app with oracle adf (Jdeveloper 10.1.2 ) and it use Oracle Domain objects.
I have an oas 10g (9.04.1) in windows
and I want to change the default jdbc driver for a single oc4j instance
in metalink i found the following information:
1.- From OTN, download and copy the 10.1.0.x JDBC driver to a directory on the server. E.g OH/newjdbc
2.- Opening EM-Website, navigate to the OC4J instance that should be altered.
3.- Find the "Java-Options" and, add the -Xbootclasspath option to it, pointing to the new JDBC driver.
E.g. -Xbootclasspath/p:$OH/newjdbc/ojdbc14.jar
4.- Restart the OC4J instance
my 'Java-optios' default is
-server -Xrs -Djava.security.policy=C:\oracle\904\j2ee\test_adf\config\java2.policy -Djava.awt.headless=true
my new 'Java optios' now is
-server -Xrs -Djava.security.policy=C:\oracle\904\j2ee\test_adf\config\java2.policy -Djava.awt.headless=true -Xbootclasspath/p = D:\jdev1012\jdbc\lib\classes12.jar
is this correct?
now I cannot deploy my app
Rigoberto

Seems you missed something in step 3. From those steps the driver should be installed under C:\oracle\904\newjdbc and used in classpath, not d:\jdev1012.

Oracle JDBC Driver 10.2.0.1.0 DataBaseMetaData Incorrect For Unary FKs

Friends,
My firm (which is not a MetaLink subscriber) has discovered a bug in the Oracle 10g JDBC Driver (10.2.0.1.0). The bug affects unary associations, namely cases in which the foreign key of a table points to that very table's primary key.
In such cases, method DatabaseMetaData.getExportedKeys (which is designed to return all foreign keys that reference a specified table) fails to return the foreign key reference. The method works correctly as long as the foreign key "points to" a different table. Example:
ResultSet lResultSetForeignKeys = aDatabaseMetaData.getExportedKeys(<foo>)
while (lResultSetForeignKeys.next())
// NOTHING RETURNED
In this case, the ResultSet contains no elements.
We discovered this problem testing the same logic against a cross-section of commercial databases. All other DBMS drivers produce the correct result except for the Oracle drivers.
If some brave soul would convert this into a MetaLink TAR we'd sure appreaciate it, and if possible we'd love to be in the loop regarding the progress on this issue. My e-mail ID is [email protected], and I'm working on behalf of Corticon Technologies, Inc.
Sincerely,
David Lynch
General Manager, SOTA

My understanding is that to be a MetaLink subscriber you have to be an Oracle customer or subscribe for Oracle support services. Since Oracle is only one of the many databases we support, and because our sole objective with Oracle is compatibility testing, it's unlikely that we will become subscribers unless it's essentially free.
Oracle is tangential (not core) to our own offerings, so we don't have a pressing need for support. Is there some avenue for people in our shoes?

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.

Oracle 8.1.7.4 + JDBC Driver 10.2.0.3.0=invalid or unknown NLS parameter...

I'm having an issue trying to update the jdbc driver from 10.1.0.2.0 to 10.2.0.3.0 to access an Oracle 8.1.7.4 instance. Using this code I'm getting the following exception, any ideas how to fix it?
Thanks,
Johann
Connection c = null;
try {
     Driver dr = new oracle.jdbc.OracleDriver();
     DriverManager.registerDriver(dr);
     Properties props = new Properties();
     props.put("user", "congiromsr");
     props.put("password", "the password");
     String url = "jdbc:oracle:thin:@cholguaco:1533:lobo";
     c = dr.connect(url, props);
     System.out.println("The driver is "
               + c.getMetaData().getDriverVersion());
     System.out.println("The DBMS is "
               + c.getMetaData().getDatabaseProductVersion());
} catch (Exception e) {
     e.printStackTrace();
} finally {
     try {
          c.close();
     } catch (Exception ignore) {
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: invalid or unknown NLS parameter value specified
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
     at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:791)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:439)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at TestClass.main(TestClass.java:14)

JDBC drivers set NLS parameters based on your locale settings. There are three based parameters: language, territory and character set. Maybe in your case JDBC driver 10.2.0.3.0 sets one of them with value that is not supported in Oracle Database 8.1.7.4. Character set is the first candidate for this. JDBC drivers use only Unicode character sets - there are a few new of them in Oracle Database 10g. 8 and 9 versions of JDBC drivers use UTF8 which is Unicode version 3.0 but in 10g is added Al32UTF8 which is Unicode version 4.0.

Deploy JDBC driver for SQL server 2005 on PI 7.1

How to deploy JDBC driver for SQL server 2005 on PI 7.1
We are in SAP NetWeaver 7.1 Oracle 10G
Third party system is SQL server 2005
There are different JDBC versions are available to download for SQL server 2005.
I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
Please help

Hi,
Hope this How to Guide help you.
How To Install and Configure External Drivers for the JDBC & JMS Adapters from
www.sdn.sap.com/irj/sdn/howtoguides
Regards,
Karthick.
Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM

Reading Advance Queuing with XMLType payload and JDBC Driver character encoding

Hi
I've got a problem retrieving the message from the queue with XMLType payload in Java.
It was working fine in 10g database but after the switch to 11g it returns corrupted string instead of real XML message. Database NLS_LANG setting is AL32UTF8
It is said that JDBC driver should deal with that automatically but it obviously don't in this case. When I dequeue the message using database functionality (DBMS_AQ package) it looks fine but not when using JDBC driver so Ithink it is character encoding issue or so. The message itself is enqueued by the database and supposed to be retrieved by dedicated EJB.
Driver file used: ojdbc6.jar
Additional libraries: aqapi.jar, xdb.jar
All file taken from 11g database installation.
What shoul dI do to get the xml message correctly?

Do you mean NLS_LANG is AL32UTF8 or the database character set is AL32UTF8? What is the database character set (SELECT value FROM nls_database_parameters WHERE parameter='NLS_CHARACTERSET')?
Thanks,
Sergiusz

In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0

Hi !
Without any problems i'm using the Oracle JDBC Driver version - 10.1.0.3.0 to access to the
Oracle database (Oracle Database 10g Release 10.2.0.1.0 - 64bit Production).
But exchanging the JDBC Driver 10.1.0.3.0 to 10.1.0.5.0 brings up the following problem:
the statement
con.prepareStatement(sql, resultSetType, resultSetConcurrency, resultSetHoldability)
(with parameters resultSetType = 1003, resultSetConcurrency = 1007, resultSetHoldability= 1)
returns null !
while using the Oracle JDBC Driver version - 10.1.0.3.0 the statement (with same parameters)
returns a correct PreparedStatement.
Every hint or idea is welcome.
Best regards,
Claus

Duplicate post:
In Trouble with the Oracle JDBC Driver version - 10.1.0.5.0
Claus,
Pardon me if I am stating the obvious, but why don't you use the 10.2 JDBC driver with your 10.2 database? The driver is part of the database distribution. Otherwise, you can download the driver from the OTN Web site.
Good Luck,
Avi.

WSAD 5.1.2Upgrading JDBC Driver to 10g

Similar Messages

Maybe you are looking for