You can translate the question and the replies:

Cognos Data Server import metadata throws null pointer

Trying to connect Cognos via Data Server to Denodo v6. Part of the steps to make a Cognos Data Server connection function is to import the metadata, which in turn then a Data Module can access. We are seeing this null pointer from the JDBC stack. Anyone seen this and where the 'null' be coming from? Cognos v11.0.7 Denodo v6 2018-01-11T08:38:45.148-0800 ERROR com.ibm.bi.platf.moser.core.tasks.ImportSchemaTask [Default Executor-thread-8598] NA NA java.sql.SQLException: Syntax error: Exception parsing query near 'null' com.ibm.cognos.jmd.exception.JMDColumnException: java.sql.SQLException: Syntax error: Exception parsing query near 'null' at com.ibm.cognos.jmd.importer.ColumnRequest.wrapException(ColumnRequest.java:205) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.AbstractedNestedJDBCRequest.getNextRow(AbstractedNestedJDBCRequest.java:80) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.JDBCResultSetIterator.getNextRow(JDBCResultSetIterator.java:111) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.AbstractResultSetIterator.skipNonMatchingRows(AbstractResultSetIterator.java:91) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.AbstractResultSetIterator.initialize(AbstractResultSetIterator.java:54) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.AbstractResultSetIterator.hasNext(AbstractResultSetIterator.java:64) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.RequestHandler.run(RequestHandler.java:60) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.JDBCImporter.execute(JDBCImporter.java:391) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.JDBCImporter.fastImport(JDBCImporter.java:789) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.JDBCImporter.importTables(JDBCImporter.java:630) ~[jmd.jar:?] at com.ibm.bi.platform.moser.core.provider.jdbc.metadata.JDBCMetadataProvider.getPhysicalModule(JDBCMetadataProvider.java:202) ~[moser-core-11.0.7-17081812.jar:11.0.7-17081812] at com.ibm.bi.platform.moser.core.tasks.ImportSchemaTask.importMetadata(ImportSchemaTask.java:596) ~[moser-core-11.0.7-17081812.jar:11.0.7-17081812] at com.ibm.bi.platform.moser.core.tasks.ImportSchemaTask.run(ImportSchemaTask.java:426) [moser-core-11.0.7-17081812.jar:11.0.7-17081812] at com.ibm.ws.concurrent.internal.SubmittedTask.run(SubmittedTask.java:276) [com.ibm.ws.concurrent_1.0.15.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522) [?:1.8.0] at java.util.concurrent.FutureTask.run(FutureTask.java:277) [?:1.8.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0] at java.lang.Thread.run(Thread.java:785) [?:?] Caused by: java.sql.SQLException: Syntax error: Exception parsing query near 'null' at com.denodo.vdb.jdbcdriver.printer.VDBJDBCPrinter.format(VDBJDBCPrinter.java:161) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.dao.DAOVDBProxy.execute(DAOVDBProxy.java:569) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.dao.DAOVDBProxy.execute(DAOVDBProxy.java:534) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.dao.DAOVDBProxy.execute(DAOVDBProxy.java:581) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.dao.DAOVDBProxy.execute(DAOVDBProxy.java:529) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.VDBJDBCStatement.executeQuery(VDBJDBCStatement.java:307) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.denodo.vdb.jdbcdriver.VDBJDBCDatabaseMetaData.getColumns(VDBJDBCDatabaseMetaData.java:627) ~[denodo-vdp-jdbcdriver.jar:6.0.0] at com.ibm.cognos.jdbc.adaptor.BaseDatabaseMetadataAdaptor.getColumnsImpl(BaseDatabaseMetadataAdaptor.java:384) ~[JDBCAdaptorSDK-11.0.7-17080911.jar:11.0.7-17080911] at com.ibm.cognos.jdbc.adaptor.BaseDatabaseMetadataAdaptor.getColumns(BaseDatabaseMetadataAdaptor.java:367) ~[JDBCAdaptorSDK-11.0.7-17080911.jar:11.0.7-17080911] at com.ibm.cognos.jmd.importer.ColumnRequest.createResultSetFromIteratorRow(ColumnRequest.java:200) ~[jmd.jar:?] at com.ibm.cognos.jmd.importer.AbstractedNestedJDBCRequest.getNextRow(AbstractedNestedJDBCRequest.java:69) ~[jmd.jar:?] ... 17 more (
Cognos
user
11-01-2018 11:50:06 -0500
code

2 Answers

Solved, had to do with the version of the JDBC drivers. We originally had v6.0 (base version it appears). After updating to v6.0 20170515 this resolved this issue.
user
11-01-2018 19:20:12 -0500
Hi, I am glad that your issue has been resolved after using an appropriate JDBC driver. In general, it is recommended to use the latest Denodo Platform update and its corresponding JDBC/ODBC drivers in order to benefit from new enhancements and bug fixes. Hope this helps!
Denodo Team
19-02-2019 23:37:58 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here