6 Replies Latest reply on Dec 19, 2017 5:32 AM by Aditi Patel

    Clob not supported in dynamic VDB

    Aditi Patel Newbie

      Hi,

       

       

      I am importing view having one of the column of clob datatype in dynamic virtual db.

      Virtual DB is successfully deployed but not able to see the data of that particular view.

       

       

      Below are is the error:

       

       

       

       

      11:31:11,658 WARN  [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (Worker5_QueryProcessorQueue72) O5LGPEM0vRiL IJ000305: Connection error occured: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@6741e862[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@4b6f9c55 connection handles=1 lastReturned=1513078271627 lastValidated=1513078271627 lastCheckedOut=1513078271627 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@25fa36a1 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@3ec4ecfe[pool=dynamicST-DS-2] xaResource=LocalXAResourceImpl@75c7433e[connectionListener=6741e862 connectionManager=42fde4e7 warned=false currentXid=null productName=Sybase IQ productVersion=SAP IQ/16.1.020.528/10528/P/sp02/Sun_x64/OS 5.11/64bit/2017-07-14 13:57:25 jndiName=java:/dynamicST-DS-2] txSync=null]: java.lang.UnsupportedOperationException: The method com.sybase.jdbc4.jdbc.SybResultSet.getClob(int) is not supported and should not be called.

              at com.sybase.jdbc4.jdbc.ErrorMessage.raiseRuntimeException(Unknown Source)

              at com.sybase.jdbc4.utils.Debug.notSupported(Unknown Source)

              at com.sybase.jdbc4.jdbc.SybResultSet.getClob(Unknown Source)

              at org.jboss.jca.adapters.jdbc.WrappedResultSet.getClob(WrappedResultSet.java:1060)

              at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:1101)

              at org.teiid.translator.jdbc.sybase.BaseSybaseExecutionFactory.retrieveValue(BaseSybaseExecutionFactory.java:124)

              at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:344)

              at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:435)

              at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:238)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:498)

              at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:220)

              at com.sun.proxy.$Proxy28.more(Unknown Source)

              at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309)

              at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)

              at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)

              at java.util.concurrent.FutureTask.run(FutureTask.java:266)

              at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)

              at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)

              at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)

              at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

              at java.lang.Thread.run(Thread.java:745)

        • 1. Re: Clob not supported in dynamic VDB
          Steven Hawkins Master

          More than likely you are using a very old jconnect driver.  Can you use a newer version?

          • 2. Re: Clob not supported in dynamic VDB
            Aditi Patel Newbie

            Hi

             

            Which is the latest jconnect driver and from where I can install that ?

             

            -Aditi

            • 4. Re: Clob not supported in dynamic VDB
              Aditi Patel Newbie

              Hi Steven

               

              I have updated the Jconnect driver. The current version is 7.07. Still I am facing some differnt error.

               

              07:47:01,145 INFO  [org.teiid.CONNECTOR] (Worker10_async-teiid-threads10)  SybaseExecutionFactory Commit=true;DatabaseProductName=Sybase IQ;DatabaseProductVersion=SAP IQ/16.1.020.528/10528/P/sp02/Sun_x64/OS 5.11/64bit/2017-07-14 13:57:25;DriverMajorVersion=7;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/7.07 SP133 (Build 27244)/P/EBF24376/JDK 1.6.0/jdbcmain/DEBUG/Thu Mar 26 04:57:02 PDT 2015;IsolationLevel=1

              07:47:02,529 INFO  [org.teiid.RUNTIME] (Worker9_async-teiid-threads9)  TEIID50030 VDB ST_VDB.1 model "SrcModel_6" metadata loaded. End Time: 12/14/17 7:47 AM

              07:47:07,194 INFO  [org.teiid.RUNTIME] (Worker8_async-teiid-threads8)  TEIID50030 VDB ST_VDB.1 model "SrcModel_2" metadata loaded. End Time: 12/14/17 7:47 AM

              07:47:58,354 INFO  [org.teiid.RUNTIME] (Worker10_async-teiid-threads10)  TEIID50030 VDB ST_VDB.1 model "SrcModel_4" metadata loaded. End Time: 12/14/17 7:47 AM

              07:48:03,510 INFO  [org.teiid.RUNTIME.VDBLifeCycleListener] (Worker10_async-teiid-threads10)  TEIID40003 VDB ST_VDB.1 is set to ACTIVE

               

              Error Log:

              07:52:45,561 ERROR [org.teiid.PROCESSOR] (Worker7_QueryProcessorQueue425) Settto6t5XMi TEIID30019 Unexpected exception for request Settto6t5XMi.32: java.lang.NullPointerException

                      at org.teiid.core.types.ClobImpl.<init>(ClobImpl.java:116)

                      at org.teiid.common.buffer.LobManager.persistLob(LobManager.java:230)

                      at org.teiid.common.buffer.LobManager.updateReferences(LobManager.java:141)

                      at org.teiid.common.buffer.TupleBuffer.addTupleBatch(TupleBuffer.java:203)

                      at org.teiid.query.processor.BatchCollector.flushBatchDirect(BatchCollector.java:230)

                      at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:686)

                      at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:224)

                      at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:195)

                      at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)

                      at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:477)

                      at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)

                      at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)

                      at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)

                      at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)

                      at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)

                      at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)

                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                      at java.lang.Thread.run(Thread.java:745)

              • 5. Re: Clob not supported in dynamic VDB
                Steven Hawkins Master

                That looks to be a bug with the getSubString method of Sybase clobs.  They are returning null when it is not expected.  We would have to workaround this with a code change.  Can you log an issue?

                 

                Steve