Error running a preview in Kepler version

<p>I have a very simple tabular form report. It works fine with Eclipse Juno but not in Eclipse Kepler. </p><p>Here are the details.</p><p> </p><p>Build where it works - Birt version 4.2.1v20120820<span> </span></p><p> </p><p>Build where it fails - Eclipse Birt version 4.3.0v201306051647</p><p> </p><p>Error - Table (id = 4912): </p><div>+ An exception occurred during processing. Please see the following message for details:</div><div>Failed to prepare the query execution for the data set: ViewAuditLogSQL</div><div>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> </div><div> </div><div>Does this mean I have not installed all the components needed for Kepler. I have seen the same problem when I integrated the latest Birt runtime and ran it under JBoss.</div><div> </div><div>I would appreciate any info on this.</div><div>Thanks,</div><div> Ravi</div>

Find more posts tagged with

Comments

micajblock

<p>Do you have the JDBC driver in the new version. You need to to make it available via the Manage Drivers in the Data Source UI.</p>

rveeraraghav

<p>Yes, I have setup JDBC driver. I get connection successful when I do a Test Connection. Also I have other reports which work except for this one. One more thing when I do a preview results on that dataset I get an error which is </p><div>A BIRT exception occurred.</div><div> Plug-in Provider:Eclipse BIRT Project</div><div> Plug-in Name:BIRT Data Engine</div><div> Plug-in ID:org.eclipse.birt.data</div><div> Version:4.3.0.v201306041519</div><div> Error Code:data.engine.InvalidBoundColumnName</div><div> Error Message:Invalid bound column name: UserName.</div>

micajblock

<p>Try re-creating the data set. If all other reports work than it is not a environment issue but more likely the data set is wrong.</p>

rveeraraghav

<p>I am confused as the report has been working ever since as back as Birt 2.3.2. ( eclipse ganymede )</p><p> </p><p>Still, I created a new report, new dataset invoking the same stored procedure. Now as I try to Preview results in the wizard 'edit Data Set' for a data source. I get an exception </p><p> </p><div>A BIRT exception occurred.</div><div> Plug-in Provider:Eclipse BIRT Project</div><div> Plug-in Name:BIRT Data Engine</div><div> Plug-in ID:org.eclipse.birt.data</div><div> Version:4.3.0.v201306041519</div><div> Error Code:odaconsumer.CannotCloseResultSet</div><div> Error Message:Cannot close the result set.</div><div> org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot close the result set.</div><div>SQL error #1:SQL Anywhere Error -260: Variable '@p0' not found</div><div> ;</div><div> com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -260: Variable '@p0' not found</div><div> </div><div>I don't understand why it has reference to a non existent variable? In fact I simplified the data set and even removed parameters by passing in hard coded values.</div><div> </div><div>One other interesting thing. I just noticed the message in Preview results which says 'Todal 500 record(s) shown. Result contains more records that are not displayed' this shows the query is executing and bringing back records.</div><div> </div><div>Also note, from Query, going to Output Columns works and it shows all the columns ( which means it is accessing the stored proc )</div>

rveeraraghav

<p>One more thing. I removed the stored procedure and used selects directly and it worked. I wonder if there is something I need to make it work with stored procedures.</p>

rveeraraghav

<p>Is this a known defect in version 4.3 where execution of a stored procedure in a dataset returns with errors? I tried one more report which invokes a stored procedure and which worked in an earlier version only to get a similar error message. Is there some changes I need to do to my report or to the stored procedures?</p><p>Thanks.</p>