AnsweredAssumed Answered

BIRT Report Parameter Error after Upgrade

Question asked by mm31375 on Jun 4, 2018
Latest reply on Jun 15, 2018 by mm31375

We have a custom reporting building block that was tested and working, however it's stopped working after an upgrade from Learn 9.1 2017 Q4 CU2 to CU3.

 

We now see an error in the stderr log that looks like this:

 

INFO   | jvm 1    | 2018/06/04 09:20:22 | Jun 04, 2018 9:20:22 AM org.eclipse.birt.data.engine.odaconsumer.ParameterMetaData getRuntimeParameterType

INFO   | jvm 1    | 2018/06/04 09:20:22 | SEVERE: Cannot get the type for parameter: 1.

INFO   | jvm 1    | 2018/06/04 09:20:22 | org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot get parameter type.

INFO   | jvm 1    | 2018/06/04 09:20:22 | SQL error #1:Unsupported feature

INFO   | jvm 1    | 2018/06/04 09:20:22 |  ;

INFO   | jvm 1    | 2018/06/04 09:20:22 |     java.sql.SQLFeatureNotSupportedException: Unsupported feature

INFO   | jvm 1    | 2018/06/04 09:20:22 | at org.eclipse.birt.report.data.oda.jdbc.ParameterMetaData.getParameterType(ParameterMetaData.java:161)

INFO   | jvm 1    | 2018/06/04 09:20:22 | at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaParameterMetaData.getParameterType(OdaParameterMetaData.java:177)

blah blah...

 

...and then later this one...

 

Jun 04, 2018 9:20:24 AM org.eclipse.birt.data.engine.odaconsumer.PreparedStatement getOdaDriverParamMetaData

INFO   | jvm 1    | 2018/06/04 09:20:24 | SEVERE: Cannot get ODA driver parameter metadata.

INFO   | jvm 1    | 2018/06/04 09:20:24 | org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot retrieve the parameter metadata.

INFO   | jvm 1    | 2018/06/04 09:20:24 | SQL error #1:ORA-00920: invalid relational operator

INFO   | jvm 1    | 2018/06/04 09:20:24 |

INFO   | jvm 1    | 2018/06/04 09:20:24 |  ;

INFO   | jvm 1    | 2018/06/04 09:20:24 |     java.sql.SQLSyntaxErrorException: ORA-00920: invalid relational operator

INFO   | jvm 1    | 2018/06/04 09:20:24 |

INFO   | jvm 1    | 2018/06/04 09:20:24 | at org.eclipse.birt.report.data.oda.jdbc.Statement.getParameterMetaData(Statement.java:936)

INFO   | jvm 1    | 2018/06/04 09:20:24 | at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQuery.getParameterMetaData(OdaQuery.java:1335)

 

The release notes don't indicate any changes to BIRT so there was nothing obvious in the release that should have affected this.  This is on a managed hosting environment so we're wondering if there was perhaps a change to the underlying database (which I will follow up with Bb support shortly).

 

If anyone has seen this kind of issue before I'd love to hear about it...

 

Thanks!

Outcomes