JDBC Driver Parametes

Hi
I am working on JDBC to JDBC Test scenario, What should I give in JDBC Driver and Connection parameters in the Sender and receiver Communication Channel
Sender and Receivers are MSSQL Servers.
Thanks
PR
Edited by: PR on Sep 10, 2009 5:34 PM
Edited by: PR on Sep 10, 2009 5:35 PM

Hi PR,
First you need to have drivers based upon the version of your sql server. Please check this link for the same:
JDBC drivers for SQL Server 2008 and PI7.0
The connection parameters should be in this format:
Error in establishing connection to SQL server
Jdbc driver format for MS Sql Server ?
Also for sql server there are few issues you may run into. For these please check this url:
http://sapxitutorials.blogspot.com/2009/07/problems-faced-while-connecting-to-sql.html
Regards,
---Satish

Similar Messages

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.

How to omit parameter values from exceptions thrown by the JDBC driver

Is there a way to get the Oracle JDBC driver to omit the parameter values from the message when it throws an exception?
We have an application that persists credit cards and when an exception is thrown by the driver, it's including the credit card number in the error message, which ultimately gets logged by the application. There are too many layers and locations, including OpenJPA, Spring, and our own application, where we'd have to massage the error data to remove that card number.
For example, we get the following exception:
Caused by: org.apache.renamed.openjpa.lib.jdbc.ReportingSQLException: ORA-20104: Permission denied
ORA-06512: at "PROTEGRITY.PTY", line 57
ORA-06512: at "PROTEGRITY.PTY", line 383
ORA-06512: at "SUBSDSYS.TORDERPAYMENT_UPD", line 16
ORA-04088: error during execution of trigger 'SUBSDSYS.TORDERPAYMENT_UPD'
{prepstmnt 6603044
UPDATE PAYMENT
SET CARD_HOLDER_NAME = ?, CARD_TYPE = ?, EXPIRY_MONTH = ?, EXPIRY_YEAR = ?, GATEWAY = ?
WHERE UIDPK = ?
[params=(String) Test Test, (String) VISA, (String) 03, (String) 2012, (String) CREDITCARD, (long) 106901]} [code=20104, state=72000]
at org.apache.renamed.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
at org.apache.renamed.openjpa.lib.jdbc.LoggingConnectionDecorator.access$800(LoggingConnectionDecorator.java:57)
The actual content of the message appears to come from the JDBC driver, not OpenJPA.
This particular example doesn't show the card number, but only exposed that possibility as a risk.
BTW: before you ask, for PCI compliance we're using a database layer service to encrypt the card numbers before they're stored in the table.
Thanks much.

[email protected] wrote:
The actual content of the message appears to come from the JDBC driver, not OpenJPA.Wrong. This is a dump of parameters used to execute a query - and it comes from some upper layer, not the JDBC driver.
I would start looking at the source code starting here:
org.apache.renamed.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)

Bug in Oracle JDBC thin driver (parameter order)

[ I'd preferably send this to some Oracle support email but I
can't find any on both www.oracle.com and www.technet.com. ]
The following program illustrates bug I found in JDBC Oracle thin
driver.
* Synopsis:
The parameters of prepared statement (I tested SELECT's and
UPDATE's) are bound in the reverse order.
If one do:
PreparedStatement p = connection.prepareStatement(
"SELECT field FROM table WHERE first = ? and second = ?");
and then bind parameter 1 to "a" and parameter to "b":
p.setString(1, "a");
p.setString(2, "b");
then executing p yields the same results as executing
SELECT field FROM table WHERE first = "b" and second = "a"
although it should be equivalent to
SELECT field FROM table WHERE first = "a" and second = "b"
The bug is present only in "thin" Oracle JDBC driver. Changing
driver to "oci8" solves the problem.
* Version and platform info:
I detected the bug using Oracle 8.0.5 server for Linux.
According to $ORACLE_HOME/jdbc/README.doc that is
Oracle JDBC Drivers release 8.0.5.0.0 (Production Release)
* The program below:
The program below illustrates the bug by creating dummy two
column table, inserting the row into it and then selecting
the contents using prepared statement. Those operations
are performed on both good (oci8) and bad (thin) connections,
the results can be compared.
You may need to change SID, listener port and account data
in getConnecton calls.
Sample program output:
$ javac ShowBug.java; java ShowBug
Output for both connections should be the same
--------------- thin Driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
[ The same - with buggy reversed order (should give no answers):
aaa
--------------- oci8 driver ---------------
[ Non parametrized query: ]
aaa
[ The same - parametrized (should give one row): ]
aaa
[ The same - with buggy reversed order (should give no answers):
--------------- The end ---------------
* The program itself
import java.sql.*;
class ShowBug
public static void main (String args [])
throws SQLException
// Load the Oracle JDBC driver
DriverManager.registerDriver(new
oracle.jdbc.driver.OracleDriver());
System.out.println("Output for both connections should be the
same");
Connection buggyConnection
= DriverManager.getConnection
("jdbc:oracle:thin:@localhost:1521:ORACLE",
"scott", "tiger");
process("thin Driver", buggyConnection);
Connection goodConnection
= DriverManager.getConnection ("jdbc:oracle:oci8:",
"scott", "tiger");
process("oci8 driver", goodConnection);
System.out.println("--------------- The end ---------------");
public static void process(String title, Connection conn)
throws SQLException
System.out.println("--------------- " + title + "
Statement stmt = conn.createStatement ();
stmt.execute(
"CREATE TABLE bug (id VARCHAR(10), val VARCHAR(10))");
stmt.executeUpdate(
"INSERT INTO bug VALUES('aaa', 'bbb')");
System.out.println("[ Non parametrized query: ]");
ResultSet rset = stmt.executeQuery(
"select id from bug where id = 'aaa' and val = 'bbb'");
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - parametrized (should give one
row): ]");
PreparedStatement prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "aaa");
prep.setString(2, "bbb");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
System.out.println("[ The same - with buggy reversed order
(should give no answers): ]");
prep = conn.prepareStatement(
"select id from bug where id = ? and val = ?");
prep.setString(1, "bbb");
prep.setString(2, "aaa");
rset = prep.executeQuery();
while (rset.next ())
System.out.println (rset.getString (1));
stmt.execute("DROP TABLE bug");
null

Horea
In the ejb-jar.xml, in the method a cursor is closed, set <trans-attribute>
to "Never".
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name></ejb-name>
<method-name></method-name>
</method>
<trans-attribute>Never</trans-attribute>
</container-transaction>
</assembly-descriptor>
Deepak
Horea Raducan wrote:
Is there a known bug in Oracle JDBC thin driver version 8.1.6 that would
prevent it from closing the open cursors ?
Thank you,
Horea

[Oracle JDBC Driver]Invalid parameter binding(s).

Hi there
I am using the OracleCachedRowSet, and it works fine until I tries to update a resultset with a null value. When I call rs.acceptChanges(connection); it results in the following exception.
Please help if anyone has found a workaround to this problem.
java.sql.SQLException: [BEA][Oracle JDBC Driver]Invalid parameter binding(s).
at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.base.BaseParameters.getParameter(Unknown Source)
at weblogic.jdbc.base.BasePreparedStatement.setObjectInternal(Unknown Source)
at weblogic.jdbc.base.BasePreparedStatement.setObject(Unknown Source)
at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:268)
at oracle.jdbc.rowset.OracleCachedRowSetWriter.updateRow(OracleCachedRowSetWriter.java:429)
at oracle.jdbc.rowset.OracleCachedRowSetWriter.writeData(OracleCachedRowSetWriter.java:534)
at oracle.jdbc.rowset.OracleCachedRowSet.acceptChanges(OracleCachedRowSet.java:2926)
at eurostat.Items.updateRS(Items.java:192)
at eurostat.DBConnectionBean.updateRS(DBConnectionBean.java:94)
at jsp_servlet.__mainpage._jspService(MainPage.jsp:248)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:246)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Hi Avi
Thanks for the suggestion, but I don't thint that is the problem. In other forums I have found people describing the same problem(both with Oracle and Sun's implementation of CachedRowSet). See this link for an example http://bugs.mysql.com/bug.php?id=9831. So I figured that those other people needed to have a solution to the problem, but I can't find it.
/Thomas

How Oracle JDBC driver determine DATE data type parameter if it is not specified

Hello,
Oracle JDBC driver determine the DATE data type of parameter correctly without any typecasting.
Example:
ps = conn.prepareStatement("SELECT ? FROM DUAL");
ps.setObject(1, Date.valueOf("2014-01-11"));
How Oracle JDBC driver determine the DATE data type of parameter.
Thought?
Regards,
Vinayak

Oracle JDBC driver determine the DATE data type of parameter correctly without any typecasting.
Example:
ps = conn.prepareStatement("SELECT ? FROM DUAL");
ps.setObject(1, Date.valueOf("2014-01-11"));
How Oracle JDBC driver determine the DATE data type of parameter.
Your question isn't clear. If the driver is doing it correctly what PROBLEM are you having? What exactly do you consider 'correct'? What results are you getting? What driver name and version are you using? What Oracle DB version are you using?
For the code you use above the 'Date' you specify is a java.sql.Date instance
http://docs.oracle.com/javase/8/docs/api/java/sql/Date.html#valueOf-java.lang.String-
public static Date valueOf(String s)
Converts a string in JDBC date escape format to a Date value.
Parameters:
s - a String object representing a date in in the format "yyyy-[m]m-[d]d". The leading zero for mm and dd may also be omitted.
Returns:
a java.sql.Date object representing the given date
The JDBC Dev Guide shows that is mapped to an oracle.sql.DATE
http://docs.oracle.com/cd/E11882_01/java.112/e16548/datacc.htm#g1028145
Oracle DATE datatypes have both date and time components. Depending on the JDBC driver version and DB version you are using an Oracle date could be mapped to a Java Date (which does NOT have a time component) or, for current versions, would be considered a timestamp..

Oracle JDBC driver - Unsupported parameter

I am getting a following message,
Unable to execute statement for table or stored procedure. 'get_PODetails' (Structure 'Statement') due to java.sql.SQLException: 'Unsupported parameter type 'SYS_REFCURSOR' for parameter 'REC1' found
While invoking stored procedure using JDBC driver. What could be the cause?

I am getting a following message,
Unable to execute statement for table or stored procedure. 'get_PODetails' (Structure 'Statement') due to java.sql.SQLException: 'Unsupported parameter type 'SYS_REFCURSOR' for parameter 'REC1' found
While invoking stored procedure using JDBC driver. What could be the cause?

Issues while configuring java application using JDO with MS JDBC Driver 1.0

We are in the process of configuring our java application with the production version of SQL Server 2005 Java Database Connectivity (JDBC) Driver 1.0. We are facing issues getting it to work with Sun App Server using JDO concept.
After creating the data store, adding the JDBC driver to the application server classpath through console and also copying the driver into the lib directory, we are still getting the below error.
Following is the stack trace encountered while running the application
[#|2006-02-15T10:21:25.493+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.entity.finder|_ThreadID=30;|JDO74010: Bean 'InventoryEJB' method ejbFindAllInventoryItems: problems running JDOQL query.
com.sun.jdo.api.persistence.support.JDOFatalInternalException: JDO76519: Failed to identify vendor type for the data store.
NestedException: java.sql.SQLException: Error in allocating a connection. Cause: javax.transaction.SystemException
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:870)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:786)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:673)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at com.sun.j2ee.blueprints.supplier.inventory.ejb.InventoryEJB1142755294_ConcreteImpl.jdoGetPersistenceManager(InventoryEJB1142755294_ConcreteImpl.java:530)
     at com.sun.j2ee.blueprints.supplier.inventory.ejb.InventoryEJB1142755294_ConcreteImpl.ejbFindAllInventoryItems(InventoryEJB1142755294_ConcreteImpl.java:146)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:147)
     at com.sun.ejb.containers.EJBLocalHomeInvocationHandler.invoke(EJBLocalHomeInvocationHandler.java:185)
     at $Proxy164.findAllInventoryItems(Unknown Source)
     at com.sun.j2ee.blueprints.supplier.inventory.web.DisplayInventoryBean.getInventory(Unknown Source)
     at org.apache.jsp.displayinventory_jsp._jspService(displayinventory_jsp.java:119)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:336)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:251)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:723)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:482)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:417)
     at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:80)
     at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:95)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:313)
     at com.sun.j2ee.blueprints.supplier.inventory.web.RcvrRequestProcessor.doPost(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:185)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
Can anyone help me on this issue?
Regards,
Bindu

I have already tried this before and this not work too, but strange that even if I use JDBC:ODBC bridge driver, the return value for output parameters are not correct, that is, only return the value that I input but not the value after executed in the procedure....
The code that I used with JDBC:ODBC bridge is as follow:
public static void main(String[] args) {
String url = "jdbc:odbc:;DRIVER=SQL Server;Persist Security Info=False;database=db;Server=sql;uid=sa;pwd=pwd";
          Connection con;
          ResultSet rs = null;
CallableStatement callS = null;
          try {
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
          } catch(java.lang.ClassNotFoundException e) {
               System.err.print("ClassNotFoundException: ");
               System.err.println(e.getMessage());
          try {
               con=DriverManager.getConnection(url);
callS = con.prepareCall("{ call dbo.CpJavaTest (?)}");
callS.registerOutParameter(1, Types.INTEGER);
callS.execute();
rs=callS.getResultSet();
int ret = callS.getInt(1);
System.out.println("return value : " + ret);
               while (rs.next()) {
                    String f1 = rs.getString(4);
                    String f2 = rs.getString(5);
                    System.out.println(f1 + " " + f2);
          } catch(SQLException ex) {
               System.out.println("SQLException: " + ex.getMessage());
The value of the output parameter is same as what I inputed! Hope any one can teach me how to correct it...
Thank you very much!

9.2.0.6 jdbc driver

Where can I get a 9.2.0.6 jdbc driver? Or does anyone know if the 9.2.0.5 jdbc driver will work for Oracle 9.2.0.6?
Thanks

I believe JDBC 9.2.0.5 driver is not fully compatible with 9.2.0.6 as I am running into problems with update query which worked fine before I patched oracle. I changed the redo log sizes when applying the patch, but don't think that should have an effect. Is anyone else running into the same problem? My update query syntax is "update [table] set [parameter]=[value] where [condition]".

Bug in Oracle JDBC Driver: NullPointerException when calling clearParameters

There is a bug in the latest version of the JDBC driver that throws a NPE when calling PreparedStatement.clearParameters(). I don't need a response to this, since I have a workaround (just catching and ignoring the exception), but it should probably be fixed. I speculate that the problem only occurs when you try to call clearParameters() more than once on the same PS, but I haven't confirmed it.
It is probably an easy fix. Following is the stack trace:
java.lang.NullPointerException
at oracle.jdbc.dbaccess.DBData.clearItem(DBData.java:431)
at oracle.jdbc.dbaccess.DBDataSetImpl.clearItem(DBDataSetImpl.java:3528)
at oracle.jdbc.driver.OraclePreparedStatement.clearParameters(OraclePreparedStatement.java:3401)
at com.solarmetric.datasource.PreparedStatementCache$CachePreparedStatement.close(PreparedStatementCache.java:293)
at com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatementBatch(SQLExecutionManagerImpl.java:666)
at com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatement(SQLExecutionManagerImpl.java:514)
at com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeInternal(SQLExecutionManagerImpl.java:406)
at com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.flush(SQLExecutionManagerImpl.java:273)
at com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:421)
at com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:549)
at com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:412)
at com.sun.jdotck.api.persistencemanager.MakePersistentAssignsObjectId.testMakePersistentAssignsObjectId2(Unknown Source)
at com.sun.jdotck.api.persistencemanager.MakePersistentAssignsObjectId.testMakePersistentAssignsObjectId(Unknown Source)
at com.sun.jdotck.api.persistencemanager.MakePersistentAssignsObjectId.runTest(Unknown Source)
at com.sun.jdotck.api.persistencemanager.PersistenceManagerTest.run(Unknown Source)
at com.solarmetric.kodo.compatibility.JDOCompatabilityTestSuite$1.runTest(JDOCompatabilityTestSuite.java:493)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:524)
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Take a look at the method that is causing the NullPointerException:
public void clearItem(int i)
if (!m_dynamic && m_vector == null && i < m_vector.size())
m_vector.removeElementAt(i);
if (m_items != null && i >= m_items.length)
return;
m_items[i] = null;
return;
A NullPointerException will be thrown whenever clearParameters() is called when no parameters have yet been bound.
The first IF statement should read:
if (!m_dynamic && m_vector != null && i < m_vector.size())
A simple workaround would be to make sure that your parameter list is never empty before calling clearParameters(). Is there a patch for this anywhere?

JDBC Driver: Messages stuck in processing started at rwb

Hi,
I have ABAP Proxy (7.1 EHP1) -> JDBC (MS SQL Server) scenario.
I'm trying to do INSERT_UPDATE. The interfases works fine for the first 5 messages. If I check the DB I see rows inserted correctly, but the first five messages stucks in processing started, and the others JDBC messages stuck in Pending to be delivered The interfase is developed as asynchron, i'm not affraid in the response.
I tryed to do just an INSERT, send just one message, or change the isolation level. But the messages continues stucking in processing started status.
One of the lasts possibilities is transform the interface to sync or increase the max number of threads of queue "JDBC_http://sap.com/xi/XI/SystemRecv" via ConfigTool. But I can't stop the j2ee stack until next weekend.
The audit Log:
- The message was successfully received by the messaging system. Protocol: XI URL: http://sapdev:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
- Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
- Message successfully put into the queue.
- The message was successfully retrieved from the receive queue.
- The message status was set to DLNG.
- Delivering to channel: CC_C0400_IM01_MES_INTEG
- JDBC Adapter Receiver processing started, required QoS ExactlyOnce
- JDBC Adapter Receiver Channel CC_C0400_IM01_MES_INTEG: processing started; party / service XXXXXXXXX_DES.
- INSERT INTO XXXXXXXXXX_TST (CodArticulo, Descripcion, EAN13, Vidautil, bolsasporestuche, estuchesporcaja, estuchesporpalet, gxu, UNISTK) VALUES (XXXXXX, XXXXXXXXX, , 270 , 1, 0 , 0.000 , 1000 , KG)
Maybe is a problem in DB side, but the experience tell me that is more inestable a SAP PI than MS SQL Server
Any Idea?
P.S. In the same PI is coexisting diferents JDBC interfaces that works fine. I have tried to use their channels but still stucking.
And this is not my first PI :P

Hi Xavier,
have a look at the documentation of this option:
db.autoCommit=NO|YES
Use this parameter to deactivate the logical unit of work required by the JDBC adapter to guarantee that the data in the database is consistent. This option is required for JDBC drivers that do not support transactions. To avoid data inconsistencies in the database when the logical unit of work is deactivated, ensure that multiple database transactions cannot access the database simultaneously.
The default value is NO.
Do not set this parameter to YES if the JDBC driver supports transactions, that is, if the system does not display a corresponding error message during normal operation.
Netweaver Documentation
I'm sure MS SQL Server JDBC Driver is able to support transactions. By default the whole message will be treated as one transaction against the database.
Regards
Sven

Issue encountered when Login as sysdba role using Thin Oracle JDBC Driver

Hello all,
we are now considering to use Thin oracle JDBC driver to create database in our project, but we met one issue when we tried to connect to oracle as sysdba role using Thin driver, and it throws java.sql.SQLException: Io Exception: SO Exception was generated, I have found some tips on oracle jdbc website and it says :
How do I connect as SYSDBA or SYSOPER?
The only way to do this is to use the Properties object when connecting, rather than specifying the username and password as strings. Put the username into the "user" property, and the password into the "password" property. Then, put the mode into the "internal_logon" property. Something like the following:
Properties props = new Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("internal_logon", "sysoper");
Connection conn = DriverManager.getConnection (url, props);
When connecting as SYSDBA or SYSOPER using the Thin driver, the RDBMS must be configured to use a password file. See "Creating and Maintaining a Password File" in the "Oracle Database Administrator's Guide".
So, i did execute orapwd command to create a password file and also set remote_login_passwordfile=execlusive in my initxxx.ora initial parameter file, however, when i tried to connect, it failed.
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
But what made me puzzled a lot is if i use OCI driver, it did work great, why??? guys, anybody knows, please give me some tips, thanks in advance.
regards,
Kaixuan @ Shanghai

clarify my question in detail:
Step 1 : create password file using orapwd command
Step 2 : create database instance using oradim command
Step 3 : login using sys as sysdba to startup database, e.g startup nomount pfile='...\initxxx.ora'
Step 4 : create database.
java code showing below:
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx ");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
issue was met here, when i tried to login as sysdba using sys, and in my java code, i use Thin driver, it then thrus exception, but when OCI driver is used, it works great, i don't know why.
that is, when i use "jdbc:oracle:oci8:@" as database URL and then properties.put("database","xxx"), it works great. but, when i use "jdbc:oracle:thin:@localhost:1521:" as database URL and then properties.put("database","xxx"), it failed. hopefully, i have clarified my question clearly. thanks.

Error in Class.forName("com.mysql.jdbc.driver")

Hi forum,
Please help me to solve the issue.
im using the following jsp code for genrating the reports using JASPER REPORTS
the JSP FILE
<%@ page contentType="text/html;charset=windows-1252"%>
<%@ page import="java.io.*"%>
<%@ page import="java.util.*"%>
<%@ page import="java.sql.*"%>
<%@ page import="javax.sql.DataSource"%>
<%@ page import="javax.naming.InitialContext"%>
<%@ page import="net.sf.jasperreports.engine.*"%>
<%@ page import="net.sf.jasperreports.engine.design.JasperDesign"%>
<%@ page import="net.sf.jasperreports.engine.xml.JRXmlLoader"%>
<%@ page import="net.sf.jasperreports.engine.export.*" %>
<%@ page import ="net.sf.jasperreports.engine.*"%>
<%@ page import ="net.sf.jasperreports.engine.JasperFillManager"%>
<%@ page import ="net.sf.jasperreports.engine.JRException"%>
<%@ page import="net.sf.jasperreports.engine.JasperReport"%>
<%@ page import="net.sf.jasperreports.engine.JasperPrint"%>
<html>
<body bgcolor="00ffcc">
<%
try{
Connection con = null;
String url="jdbc:mysql://localhost/customer";
String username = "root";
String password = "cmsadmin";
InputStream input=new FileInputStream(new File("C:/Documents and Settings/user/My Documents/NetBeansProjects/jasperreports/web/helloworld.xml"));
JasperDesign design = JRXmlLoader.load(input);
JasperReport report = JasperCompileManager.compileReport(design);
Map params = new HashMap();
params.put("reportTitle", "helloworld");
params.put("author", "Muthu Kumar");
params.put("startDate", (new java.util.Date()).toString());
params.put("ReportTitle", "PDF JasperReport");
<img class="emoticon" src="images/emoticons/confused.gif" border="0" alt="" />Class.forName("com.mysql.jdbc.Driver");<img class="emoticon" src="images/emoticons/confused.gif" border="0" alt="" /><img src="images/emoticons/confused.gif" border="0" alt="" />
con = DriverManager.getConnection(url,username,password);
JasperPrint print = JasperFillManager.fillReport(report, params, con);
OutputStream output=new FileOutputStream(new File("C:/Documents and Settings/user/My Documents/NetBeansProjects/jasperreports/helloreportworld.pdf"));
JasperExportManager.exportReportToPdfStream(print, output);
// JasperViewer.viewReport(print);
catch(SQLException es) {
out.println(es);
catch(JRException ex){
//ex.printStackTrace();
out.println(ex);
%>
</body>
</html>The error it is saying is in the line Class.forName(....) ;
Please look for the emoctions with question mark
i DOn know what to do.
Please help
Im comparin the below JRXML file as with the above code
<?xml version="1.0"?>
<!DOCTYPE jasperReport
PUBLIC "-//JasperReports//DTD Report Design//EN"
"http://jasperreports.sourceforge.net/dtds/jasperreport.dtd">
<jasperReport name="helloworld">
<parameter name="reportTitle" class="java.lang.String"/>
<parameter name="author" class="java.lang.String"/>
<parameter name="startDate" class="java.lang.String"/>
<queryString>
<![CDATA[SELECT * FROM customer order by UserID ]]>
</queryString>
<field name="UserID" class="java.lang.String"/>
<field name="UserName" class="java.lang.String"/>
<field name="City" class="java.lang.String"/>
<field name="State" class="java.lang.String"/>
<title>
<band height="60">
<textField>
<reportElement x="0" y="10" width="500" height="40"/>
<textElement textAlignment="Center">
<font size="24"/>
</textElement>
<textFieldExpression class="java.lang.String">
<![CDATA[$P{reportTitle}]]>
</textFieldExpression>
</textField>
<textField>
<reportElement x="0" y="40" width="500" height="20"/>
<textElement textAlignment="Center"/>
<textFieldExpression class="java.lang.String">
<![CDATA["Run by: " + $P{author}
+ " on " + $P{startDate}]]>
</textFieldExpression>
</textField>
</band>
</title>
<columnHeader>
<band height="30">
<rectangle>
<reportElement x="0" y="0" width="500" height="25"/>
<graphicElement/>
</rectangle>
<staticText>
<reportElement x="5" y="5" width="50" height="15"/>
<textElement/>
<text><![CDATA[UserID]]></text>
</staticText>
<staticText>
<reportElement x="55" y="5" width="150" height="15"/>
<text><![CDATA[UserName]]></text>
</staticText>
<staticText>
<reportElement x="205" y="5" width="255" height="15"/>
<text><![CDATA[City, State]]></text>
</staticText>
</band>
</columnHeader>
<detail>
<band height="20">
<textField>
<reportElement x="5" y="0" width="50" height="15"/>
<textElement/>
<textFieldExpression class="java.lang.String">
<![CDATA[$F{UserID}]]>
</textFieldExpression>
</textField>
<textField>
<reportElement x="55" y="0" width="150" height="15"/>
<textElement/>
<textFieldExpression class="java.lang.String">
<![CDATA[$F{UserName}]]>
</textFieldExpression>
</textField>
<textField>
<reportElement x="205" y="0" width="255" height="15"/>
<textElement/>
<textFieldExpression class="java.lang.String">
<![CDATA[$F{City} + ", " + $F{State}]]>
</textFieldExpression>
</textField>
</band>
</detail>
</jasperReport>

Glass_Fish wrote:
I have set the classpath in the environment variables in the my computer properties.The web container has it's own properties. The "system" classpath means absolutely nothing to it. Read your server's documentation.

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

JNDI-Tomcat 5.5.17, Cannot create JDBC driver of class '' for connect URL '

I wrote a jsp program using JNDI to get connected to MySql DB, but i got the error " Cannot load JDBC driver class 'com.mysql.jdbc.Driver' " while running the program.
I'm using NetBean5.5 which has bundled TomCat5.5.17.
I've refered to many tutorials and websites, but i still can't solve it, here's my configuration and codes:
Imported mysql-connector-java-5.0.5-bin into lib directory.
context.xml:
<Context path="/WebApplication1">
<Resource name="jdbc/jsp" auth="Container" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/jsp">
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/jsp</value>
</parameter>
<parameter>
<name>username</name>
<value>root</value>
</parameter>
<parameter>
<name>password</name>
<value>malaysia</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>20</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>10</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>-1</value>
</parameter>
</ResourceParams>
</Context>
i included the following in Web.xml:
<resource-ref>
<res-ref-name>jdbc/jsp</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
My JSP Code:
Context initContext = new InitialContext();
Context envContext = (Context)initContext.lookup("java:/comp/env");
DataSource ds = (DataSource)envContext.lookup("jdbc/jsp");
Connection conn = ds.getConnection();
Thanks~~~~

I think mysql jdbc library should add to the class library path of your project.
Hope this helps.

JDBC Driver Parametes

Similar Messages

Maybe you are looking for