Hello.
Today I discovered the following issue. I can not get data via Database Reader or Database Connector from views which have russian symbols in their names. Database Reader returnes error “ERROR Database Reader Execute failed: Operation not yet supported”. And Database Connector returns nothing. When I tried to select from table with only enlish symbols in name from the same Database server all ok. This server has special authorization - servers’s name is “AS-MSK-A0014\NSI”, not just “AS-MSK-A0014”. But I can make select in Database Reader or in Database Connector from views with russian symbols in their names from other Database Servers which has Windows Authentication. The names of such succesfull servers like “AS-MSK-A0014” not like “AS-MSK-A0014<something>”. Both servers have the same driver in ODBC - “SQL Server”. So it seems the issue connected not only with russian symbols, but with database authentication method.
Hi simulyant,
I am not sure, if I perfectly understand your problem: If the table or view name contains Russian symbols, you can’t read data from the database into KNIME. If you change the table name (without Russian symbols) everything works fine. Is this correct? Would it be possible that you send my the full stack trace from the Console log (need to change KNIME GUI preferences to DEBUG level) from the exception “Operation not yet supported” above.
Regards, Thomas
Hello, gabriel. You understand wrong. Database Reader (Database Connector) IN SOME CASES CAN read views with russian symbols in their names, but iIN SOME CASES THEY CAN NOT read views with russian symbols in their name. In such cases error “ERROR Database Reader Execute failed: Operation not yet supported” appeares in KNIME Console. I beleive that the difference in such cases connects with the type of database authentication. In one case I connect to server “”. In this case Windows Authentication used. And in another case I connect to server “<databasename>”. I told this authentication named “SSPI”.
Here is the stack trace from the Console log with DEBUG level:
DEBUG WorkflowContextMenuProvider Building up context menu…
DEBUG WorkflowContextMenuProvider selected edit part: NodeContainerEditPart( Database Reader 0:5:4 (CONFIGURED) )
DEBUG WorkflowContextMenuProvider adding open node-view action(s) to context menu…
DEBUG WorkflowContextMenuProvider adding open port-view action(s) to context menu…
DEBUG ExecuteAction Creating execution job for 1 node(s)…
DEBUG NodeContainer Database Reader 0:5:4 has new state: MARKEDFOREXEC
DEBUG NodeContainer Database Reader 0:5:4 has new state: QUEUED
DEBUG KnimeResourceNavigator state changed to EXECUTING
DEBUG NodeContainer Workflow Manager 0:5 has new state: EXECUTING
DEBUG NodeContainer Workflow Manager 0 has new state: EXECUTING
DEBUG WorkflowManager Database Reader 0:5:4 doBeforeExecute
DEBUG NodeContainer Database Reader 0:5:4 has new state: EXECUTING
DEBUG NodeContainer Workflow Manager 0:5 has new state: EXECUTING
DEBUG Database Reader Start execute
DEBUG Database Reader reset
DEBUG Database Reader clean output ports.
ERROR Database Reader Execute failed: Operation not yet supported
DEBUG Database Reader Execute failed: Operation not yet supported
java.lang.UnsupportedOperationException: Operation not yet supported
at sun.jdbc.odbc.JdbcOdbcResultSet.getNString(Unknown Source)
at org.knime.core.node.port.database.DatabaseReaderConnection$DBRowIterator.readNString(DatabaseReaderConnection.java:523)
at org.knime.core.node.port.database.DatabaseReaderConnection$DBRowIterator.next(DatabaseReaderConnection.java:380)
at org.knime.core.node.ExecutionContext.createBufferedDataTable(ExecutionContext.java:148)
at org.knime.core.node.port.database.DatabaseReaderConnection.createTable(DatabaseReaderConnection.java:174)
at org.knime.base.node.io.database.DBReaderNodeModel.execute(DBReaderNodeModel.java:79)
at org.knime.core.node.NodeModel.execute(NodeModel.java:556)
at org.knime.core.node.NodeModel.executeModel(NodeModel.java:410)
at org.knime.core.node.Node.execute(Node.java:653)
at org.knime.core.node.workflow.SingleNodeContainer.executeNode(SingleNodeContainer.java:587)
at org.knime.core.node.workflow.SingleNodeContainer.access$1(SingleNodeContainer.java:561)
at org.knime.core.node.workflow.SingleNodeContainer$1.run(SingleNodeContainer.java:446)
at org.knime.core.node.workflow.JobRunnable.run(JobRunnable.java:43)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at org.knime.core.util.ThreadPool$MyFuture.run(ThreadPool.java:98)
at org.knime.core.util.ThreadPool$Worker.run(ThreadPool.java:166)
DEBUG Database Reader reset
DEBUG Database Reader clean output ports.
DEBUG Database Reader Configure succeeded. (Database Reader)
DEBUG WorkflowManager Database Reader 0:5:4 doAfterExecute - failure
DEBUG NodeContainer Database Reader 0:5:4 has new state: CONFIGURED
DEBUG KnimeResourceNavigator state changed to CONFIGURED
DEBUG NodeContainer Workflow Manager 0:5 has new state: CONFIGURED
DEBUG NodeContainer Workflow Manager 0 has new state: IDLE
DEBUG NodeContainer Workflow Manager 0:5 has new state: CONFIGURED
Hi, that’s the same problem as decribed here http://www.knime.org/node/617. Will be fixed in the next release! Cheers, Thomas