nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A report which worked in 3.7.2 gives an error in 4.3.2

rveeraraghav

<p>I have a Birt report where I use SQL based data sets. The datasets are basically stored procedures. </p><p>These stored procedures store the results in temp tables which are created as 'local temporary tables' and added 'on commit preserve rows'. The columns ( all of them ) are declared as varchar. In Birt they are translated as String. </p><p> </p><p>This report worked fine in 3.7.2. When upgraded to Birt 4.3.2, I get an error when trying to run this report deployed to the server. I am unable to figure out what could possibly be the reason for this failure. </p><p> </p><p>Here is stack trace. ( just the first few lines of it ). </p><p> </p><p>Any ideas?</p><p>Thanks,</p><p> Ravi</p><p> </p><div>May 19, 2014 1:46:27 PM org.eclipse.birt.data.engine.odaconsumer.ResultSetMetaData getColumnNativeTypeName</div><div>SEVERE: Cannot get the native data type name for column: 1</div><div>org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot get the column type name.</div><div>SQL error #1:SQL Anywhere Error -260: Variable '@p_tds_rpc0' not found</div><div> ;</div><div> com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -260: Variable '@p_tds_rpc0' not found</div><div>at org.eclipse.birt.report.data.oda.jdbc.ResultSetMetaData.getColumnTypeName(ResultSetMetaData.java:245)</div><div>at org.eclipse.birt.report.data.oda.jdbc.bidi.BidiResultSetMetaData.getColumnTypeName(BidiResultSetMetaData.java:68)</div><div>at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaResultSetMetaData.getColumnTypeName(OdaResultSetMetaData.java:193)</div><div>at org.eclipse.birt.data.engine.odaconsumer.ResultSetMetaData.getColumnNativeTypeName(ResultSetMetaData.java:175)</div><div>at org.eclipse.birt.data.engine.odaconsumer.ProjectedColumns.<init>(ProjectedColumns.java:58)</div><div>at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.doGetProjectedColumns(PreparedStatement.java:433)</div><div>at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.getProjectedColumns(PreparedStatement.java:378)</div><div>at org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.declareCustomColumn(PreparedStatement.java:1223)</div><div>at org.eclipse.birt.data.engine.executor.DataSourceQuery.addCustomFields(DataSourceQuery.java:686)</div><div>at org.eclipse.birt.data.engine.executor.DataSourceQuery.prepareColumns(DataSourceQuery.java:409)</div><div>at org.eclipse.birt.data.engine.executor.DataSourceQuery.prepare(DataSourceQuery.java:347)</div><div>at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery$OdaDSQueryExecutor.prepareOdiQuery(PreparedOdaDSQuery.java:517)</div><div>at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:346)</div><div>at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:463)</div><div> </div><div>.................</div>

Find more posts tagged with

Comments

rveeraraghav

<p>Additional info - Just to eliminate the possibility that there could be an issue with my stored procedure, I wrote a tiny java program to execute and print the results - this works fine and displays all the results, similar to what Birt 3.7.2 did. This leads me to suspect some JDBC driver change in Birt 4.3.2 from Birt 3.7.2</p><p> </p><p>Further additional info - for the database - I am using Sybase SQL Anywhere version 11. </p><p> </p><p>Also the jdbc jar I used in java to test is - jconn3-6.05.jar</p><p> </p><p>Any suggestions/hints to solve this problem will be appreciated. I have more than 40 reports in the project and this is the only one which has issues.</p><p> </p><p>Thanks,</p><p> Ravi</p>

rveeraraghav

<p>An update to this weird situation. I changed my report from using a JDBC Data Source to a scripted data source, wrote a small java class which has jdbc calls to execute the stored procedures and created Scripted Data Set to access the data - <strong>with these changes my report works!</strong> My only guess as to why it was not working in the first place is, something is not compatible or not working with oda jdbc driver - can't explain any other way. Basically I just want to say if someone gets stuck with this sort of jdbc driver issue to try out scripted data source.</p>

mwilliams

<p>I don't have SyBase to test this and I've not heard of anyone else having this issue. On their website, the error you're getting is explained by:</p><p> </p><p>[color=rgb(0,0,0);font-family:sans-serif;font-size:13px;]You attempted to DROP or SET the value of a SQL variable that was not created or was previously dropped[/color]</p><p> </p><p>[color=rgb(0,0,0);font-family:sans-serif;font-size:13px;]Obviously your query must be okay if it's working in other methods, just not through the JDBC data source, so I would guess it must be a bug. Any way you could download BIRT 4.4 and/or an earlier version of 4.3.x to test this on?[/color]</p>

rveeraraghav

<p>Hi Michael,</p><p> I will check the stored procedures again to see what variable could be causing this issue. You are right, the stored procedure works fine when the same exact report is executed under Birt 3.7.2 ( Birt 3.7.2 runtime is used in our product right now ). The problem is only with Birt 4.3.2. Also the same exact stored procedure when invoked from java code, used as a scripted data source works as well. Finally, I managed to create a small Test table with a few columns, a report to access it and a stored procedure which creates a temp table, populates the table and returns the results - this scenario which is a tinier version of what I have also does not work, though the error itself is slightly different. </p><p>Thanks,</p><p> Ravi</p>

mwilliams

<p>When you create your dataSet, are you using the "stored procedure" option from the drop down in the first screen of the dataSet wizard?</p>

rveeraraghav

<p>Yes I have. Tried both ways as a regular sql select query as well as a sql stored procedure query. What is puzzling is, it works so well under Birt 3.7.2. or using a scripted data source - we are moving to 4.3.2 as it has addressed many other issues which were there in 3.7.2</p><p>Thanks,</p><p> Ravi</p>

mwilliams

<p>Please log a bug for this in the eclipse.org bugzilla. You'll find a link in the community section of the eclipse.org/birt site.</p><p> </p><p>Would you mind downloading the latest build of 4.4 to see if it still has this issue?</p>