com.sap.db.jdbc.exceptions.JDBCDriverException

SAP DBTech JDBC: [340]: not all variables bound: unbound parameter : 1 of 4

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web16

  • via GitHub by tbealby
    ,
  • via GitHub by 739823891
    ,
  • Stack trace

    • com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [340]: not all variables bound: unbound parameter : 1 of 4 at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345) at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:185) at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:100) at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1130) at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:877) at com.sap.db.jdbc.StatementSapDB.sendCommand(StatementSapDB.java:932) at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:981) at com.sap.db.jdbc.StatementSapDB.execute(StatementSapDB.java:256) at com.sap.db.jdbc.StatementSapDB.execute(StatementSapDB.java:228) at com.sap.db.jdbc.trace.Statement.execute(Statement.java:79) at com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:197) at com.bloidonia.vertx.mods.JdbcProcessor.doExecute(JdbcProcessor.java:312) at com.bloidonia.vertx.mods.JdbcProcessor.doExecute(JdbcProcessor.java:296) at com.bloidonia.vertx.mods.JdbcProcessor.handle(JdbcProcessor.java:210) at com.bloidonia.vertx.mods.JdbcProcessor.handle(JdbcProcessor.java:47) at org.vertx.java.core.eventbus.impl.DefaultEventBus$7.run(DefaultEventBus.java:689) at org.vertx.java.core.impl.DefaultContext$3.run(DefaultContext.java:170) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,