com.sybase.jdbc3.utils.UnimplementedOperationException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • (minor) 07:24:41,184 [main] WARN (JDBCExceptionReporter.java:49) - 010SK: Unable to set database option SET_CATALOG. (major) Exception in thread "main" com.sybase.jdbc3.utils.UnimplementedOperationException: Methode com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(String, int) is not implemented and should not be called. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(ErrorMessage.java:957) at com.sybase.jdbc3.utils.Debug.notImplemented(Debug.java:387) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(SybConnection.java:916) with jconn2 driver one will get: Exception in thread "main" java.lang.AbstractMethodError: com.sybase.jdbc2.jdbc.SybConnection.prepareStatement(Ljava/lang/String;I)Ljava/sql/PreparedStatement; 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.hibernate.util.GetGeneratedKeysHelper.prepareStatement(GetGeneratedKeysHelper.java:39) ... BTW: It would be nice, if you could issue a warning, if one uses @UniqueConstraint(columnNames = { "firstname", "lastname" } and @Column(name="firstname", nullable=true, length=255) public String getFirstname() { ... } In this case, Sybase Anywhere converts silently the 'firstname' column to 'NOT NULL' and if one tries to insert a null value ...
    via by Jens Elkner,
  • (minor) 07:24:41,184 [main] WARN (JDBCExceptionReporter.java:49) - 010SK: Unable to set database option SET_CATALOG. (major) Exception in thread "main" com.sybase.jdbc3.utils.UnimplementedOperationException: Methode com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(String, int) is not implemented and should not be called. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(ErrorMessage.java:957) at com.sybase.jdbc3.utils.Debug.notImplemented(Debug.java:387) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(SybConnection.java:916) with jconn2 driver one will get: Exception in thread "main" java.lang.AbstractMethodError: com.sybase.jdbc2.jdbc.SybConnection.prepareStatement(Ljava/lang/String;I)Ljava/sql/PreparedStatement; 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.hibernate.util.GetGeneratedKeysHelper.prepareStatement(GetGeneratedKeysHelper.java:39) ... BTW: It would be nice, if you could issue a warning, if one uses @UniqueConstraint(columnNames = { "firstname", "lastname" } and @Column(name="firstname", nullable=true, length=255) public String getFirstname() { ... } In this case, Sybase Anywhere converts silently the 'firstname' column to 'NOT NULL' and if one tries to insert a null value ...
    via by Jens Elkner,
  • getHoldability() has not been completed
    via by Kalpesh Soni,
  • GitHub comment 221#11483468
    via GitHub by pengyucai
    ,
  • SQLExplorer 3.5.0 beta 2
    via eclipsesql by spackers
    ,
  • hi i downloaded latest quartz 2.2.1, and want to use it with our sybase database but i encountered some issues. I'm trying to work out if this project is still actively supported by you as 2.2.1 is not in the released versions in this jira (it's in unreleased) and this issue seems old judging by comments on your forums 1) there are mismatches between the column widths in the db schema scripts I had to change QRTZ_SIMPROP_TRIGGERS.TRIGGER_GROUP and TRIGGER_NAME to be varchar(200) instead of varchar(80) which is what was in the scripts in the distribution, otherwise there were errors when i ran the tables in. 2) quartz jdbc data store is not working with the c3p0 version 0.9.1.1 and - i get exceptions around getHoldability() not yet implemented. this is the same version I use with hibernate 4.2.1Final. i'm using jConnect for JDBC 3.0 Is there a way to make quartz not use c3p0, or another way around this? I would rather not downgrade the c3p0 version I'm using to match what quartz (may) work with thanks quartz.properties: org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.SybaseDelegate org.quartz.jobStore.dataSource = myDS org.quartz.dataSource.myDS.driver = com.sybase.jdbc3.jdbc.SybDriver org.quartz.dataSource.myDS.URL = jdbc:sybase:Tds:efx-db-dev.ib.internal:..... org.quartz.dataSource.myDS.user = ..... org.quartz.dataSource.myDS.password = ....... org.quartz.dataSource.myDS.maxConnections = 30 org.quartz.scheduler.skipUpdateCheck = true org.quartz.threadPool.threadCount = 10 that exception : 2013-10-03 12:03:04,857 [DEBUG ] com.mchange.v2.resourcepool.BasicResourcePool : An exception occurred while acquiring a poolable resource. Will retry. com.sybase.jdbc3.utils.UnimplementedOperationException: The method com.sybase.jdbc3.jdbc.SybConnection.getHoldability() has not been completed and should not be called. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(ErrorMessage.java:957) at com.sybase.jdbc3.utils.Debug.notImplemented(Debug.java:387) at com.sybase.jdbc3.jdbc.SybConnection.getHoldability(SybConnection.java:1482) at com.mchange.v2.c3p0.impl.NewPooledConnection.<init>(NewPooledConnection.java:106) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:198) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
    via by John Murray,
  • hi i downloaded latest quartz 2.2.1, and want to use it with our sybase database but i encountered some issues. I'm trying to work out if this project is still actively supported by you as 2.2.1 is not in the released versions in this jira (it's in unreleased) and this issue seems old judging by comments on your forums 1) there are mismatches between the column widths in the db schema scripts I had to change QRTZ_SIMPROP_TRIGGERS.TRIGGER_GROUP and TRIGGER_NAME to be varchar(200) instead of varchar(80) which is what was in the scripts in the distribution, otherwise there were errors when i ran the tables in. 2) quartz jdbc data store is not working with the c3p0 version 0.9.1.1 and - i get exceptions around getHoldability() not yet implemented. this is the same version I use with hibernate 4.2.1Final. i'm using jConnect for JDBC 3.0 Is there a way to make quartz not use c3p0, or another way around this? I would rather not downgrade the c3p0 version I'm using to match what quartz (may) work with thanks quartz.properties: org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.SybaseDelegate org.quartz.jobStore.dataSource = myDS org.quartz.dataSource.myDS.driver = com.sybase.jdbc3.jdbc.SybDriver org.quartz.dataSource.myDS.URL = jdbc:sybase:Tds:efx-db-dev.ib.internal:..... org.quartz.dataSource.myDS.user = ..... org.quartz.dataSource.myDS.password = ....... org.quartz.dataSource.myDS.maxConnections = 30 org.quartz.scheduler.skipUpdateCheck = true org.quartz.threadPool.threadCount = 10 that exception : 2013-10-03 12:03:04,857 [DEBUG ] com.mchange.v2.resourcepool.BasicResourcePool : An exception occurred while acquiring a poolable resource. Will retry. com.sybase.jdbc3.utils.UnimplementedOperationException: The method com.sybase.jdbc3.jdbc.SybConnection.getHoldability() has not been completed and should not be called. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(ErrorMessage.java:957) at com.sybase.jdbc3.utils.Debug.notImplemented(Debug.java:387) at com.sybase.jdbc3.jdbc.SybConnection.getHoldability(SybConnection.java:1482) at com.mchange.v2.c3p0.impl.NewPooledConnection.<init>(NewPooledConnection.java:106) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:198) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
    via by John Murray,
  • Quartz jobstore doesn't work with sybase 15
    via by albertP,
    • com.sybase.jdbc3.utils.UnimplementedOperationException: Methode com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(String, int) is not implemented and should not be called. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(ErrorMessage.java:957) at com.sybase.jdbc3.utils.Debug.notImplemented(Debug.java:387) at com.sybase.jdbc3.jdbc.SybConnection.prepareStatement(SybConnection.java:916)

    Users with the same issue

    Unknown visitor1 times, last one,